Systems, apparatus, and methods of checkpoint summary based monitoring for an event candidate related to an ID node within a wireless node network

ABSTRACT

Systems, apparatus, and methods are described for checkpoint summary based monitoring for an event candidate within a wireless node network of ID nodes, a master node, and a server. Such a method, for example, may have the master node receiving a first set of advertising signals broadcast by an ID node and generating a first checkpoint summary representing the first set of received signals. The master node then receives a second set of advertising signals broadcast by the ID node (after the ID node broadcasts the first set) and generates a second checkpoint summary representing the second set of received signals. The method then identifies the event candidate based upon a comparison of an observed parameter for each of the first checkpoint summary and the second checkpoint summary; and reports to the server a message about the event candidate relative to the ID node.

PRIORITY AND RELATED APPLICATIONS

The present application hereby claims the benefit of priority to relatedProvisional Patent Application No. 62/189,911 and entitled “Methods andSystems for Enhanced Monitoring for an Event Candidate and AdaptiveManagement of a Wireless Node Network Based Upon the Event Candidate”,which was filed on Jul. 8, 2015.

The present application is also related in subject matter to thefollowing non-provisional patent applications where each also claims thebenefit of priority to the same above-referenced provisional patentapplication: (1) Non-Provisional patent application Ser. No. 15/166,926entitled “Systems, Apparatus, and Methods of Event Monitoring for anEvent Candidate Related to an ID Node within a Wireless Node Network”;(2) Non-Provisional patent application Ser. No. 15/167,001 entitled“Systems, Apparatus, and Methods of Event Monitoring for an EventCandidate within a Wireless Node Network Based Upon Sighting Events,Sporadic Events, and Benchmark Checkpoint Events”; (3) Non-Provisionalpatent application Ser. No. 15/167,212 entitled “Systems, Apparatus, andMethods of Time Gap Related Monitoring for an Event Candidate Related toan ID Node within a Wireless Node Network”; (4) Non-Provisional patentapplication Ser. No. 15/167,429 entitled “Systems, Apparatus, andMethods of Enhanced Monitoring for an Event Candidate Associated withCycling Power of an ID Node within a Wireless Node Network”; (5)Non-Provisional patent application Ser. No. 15/168,463 entitled“Systems, Apparatus, and Methods of Enhanced Checkpoint Summary BasedMonitoring for an Event Candidate Related to an ID Node within aWireless Node Network”; (6) Non-Provisional patent application Ser. No.15/168,482 entitled “Systems, Apparatus, and Methods of EnhancedManagement of a Wireless Node Network Based Upon an Event CandidateRelated to Elements of the Wireless Node Network.”

FIELD OF THE DISCLOSURE

The present disclosure generally relates to systems, apparatus andmethods in the field of tracking items (e.g., an object, a package, aperson, a piece of equipment) with elements of a wireless node networkand, more particularly, to various aspects involving systems, apparatusand methods for enhanced monitoring for an event candidate related to astatus of elements of a wireless node network and adaptive management ofthe wireless node network based upon the event candidate.

BACKGROUND

Asset management has always been an important part of commerce, and theability to identify an item and locate its whereabouts may be consideredcore to companies that ship items from one location to another. Forexample, tracking packages is important to organizations of all kinds,whether it be a company keeping track of inventory to be sold in itsstores, or a package delivery provider keeping track of packages beingtransported through its delivery network. To provide quality service, anorganization typically creates and maintains a highly organized networkfor tracking its items—packages, people, objects, etc. Effectivemanagement of such networks allows lower cost, reduced delivery time,and enhanced customer service. And efficient deployment of the networkhelps manage costs.

In addition to tracking packages, parties that ship and receive packagesmay also need information regarding the conditions of the packages, suchas the temperature and humidity of the package. For example, a customerthat has ordered a box of wine may want to monitor the temperature ofthe contents of the box to determine if the temperature and/or humiditygoes above or below a set range. Likewise, the party that ships thepackage may also want to monitor the conditions of the package to ensurethat the content arrives in the proper condition.

Conventionally, this tracking function may be provided by a variety ofknown mechanisms and systems. Machine-readable barcodes are one wayorganizations keep track of items. A retailer, for example, may use barcodes on items in its inventory. For example, items to be sold in aretailer's store may each be labeled with a different machine-readablebar code. In order to keep track of inventory, the retailer typicallyscans or otherwise captures an image of the bar code on each item sothat a back-end part of the retailer's operation can keep track of whatis coming in and leaving their possession from suppliers. In addition,when an item is sold to a consumer, the bar code for that item isscanned or captured to track sales and inventory levels.

Similarly, a package delivery provider may utilize machine-readable barcodes by associating a bar code with packages to be delivered to arecipient. For example, a package may have a bar code corresponding to atracking number for that package. Each time the package goes through atransit checkpoint (e.g., the courier taking initial control of thepackage, the package being temporarily placed in a storage facilitywhile being moved from a pickup point to a delivery location, and thepackage being delivered to the recipient, etc.), the package's bar codemay be scanned. Bar codes, however, have the disadvantage that personnelmust manually scan each bar code on each item in order to effectivelytrack the items.

Radio-frequency identification (RFID) tags are another known mechanismfor tracking items. In contrast to barcodes, RFID tags do not usuallyrequire manual scanning. For example, in a retail context, an RFID tagon an inventory item may be able to communicate with an electronicreader that detects items in a shopping cart and adds the cost of eachitem to a bill for the consumer. The RFID tag usually transfers a codednumber when queried or prompted by the reader. RFID tags have also beenused to track items such as livestock, railroad cars, trucks, and evenairline baggage. These tags typically only allow for basic tracking, butdo not provide a way to improve asset management using information aboutthe environment in which the items are tracked.

Sensor-based tracking systems are also known which can provide moreinformation than RFID systems. Shippers, carriers, recipients, and otherparties often wish to know the location, condition, and integrity ofshipments before, during, and after transport to satisfy quality controlgoals, meet regulatory requirements, and optimize business processes.However, such systems are typically expensive given the complexity ofthe sensors, and may provide extraneous and redundant item information.

An additional challenge faced for tracking systems may be how to monitorand keep abreast of what is going on at a low level of the networkwithout overloading or unduly stressing communications with a backendserver that operates to manage elements of the networked system.Monitoring of nodes in a network of wireless nodes may generate arelatively large amount of data—e.g., time series scanning data on whatis detected as being broadcast by particular nodes. The status of nodestypically changes over time, and thus the data generated when monitoringnodes will be dynamic and change over time to reflect such node behaviorand changing status. As a result, monitoring systems are usually facedwith a challenge on how to efficiently identify, report, and respond torelevant changes with respect to nodes amidst such vast amounts of data.Additionally, conventional tracking systems do not typically monitor thestatus of individual elements to collectively learn from what is beingmonitored so that it can identify that what is going on may be tied toknown, anticipated, or new node relevant activity.

To address one of more of such challenges, a wireless node-based systemis needed that may monitor data regarding objects (such as shippeditems, personnel, or equipment) and efficiently extend visibility ofsuch objects. There remains a need for an improved system that mayprovide more extensive and robust identification, tracking, andmanagement of objects via different types of wireless nodes and managingbackend servers and do so in a cost effective manner. In particular,there remains a need for systems, apparatus and methods for enhancedmonitoring for an event candidate related to elements of a wireless nodenetwork and adaptive management of the wireless node network based uponthe event candidate.

SUMMARY

In the following description, certain aspects and embodiments aregenerally directed to providing a technical solution for an enhancedlogistics monitoring operation that monitors for an event candidaterelated to elements of a wireless node network having low-level IDnodes, a master node at a mid-level of the network in communication withthe ID nodes, and a server at a higher level of the network incommunication with the master node. It should be understood that theaspects and embodiments, in their broadest sense, could be practicedwithout having one or more features of these aspects and embodiments. Itshould be understood that these aspects and embodiments are merelyexemplary.

For example, one aspect of the disclosure focuses on an improvedmonitoring system that identifies an event candidate within a wirelessnode network based upon checkpoint summaries. The system generallyincludes a server disposed at a top level of the wireless node network;an ID node disposed at a low level of the wireless node network; and amaster node disposed at a middle level of the wireless node network. Themaster node is an enhanced monitoring intermediary element of thewireless node network that improves overall performance of the networkby reducing the need for ID node status related transmissions to theserver when attempting to keep the server informed of what is happeningwithin the wireless node network. In particular, the system's masternode has at least a master node processing unit (e.g., a processor orprocessor based controller), a memory storage, and two differentcommunication interfaces. Each of the memory storage and communicationinterfaces is coupled to the master node processing unit. A first of thecommunication interfaces is operative to communicate directly the IDnode over a first communication path (e.g., a Bluetooth® formatted shortrange path) while a second of the communication interfaces is operativeto communicate directly with the server over a second communication path(e.g., a Wi-Fi or cellular path) that is different from the firstcommunication path.

Furthermore, the master node's memory storage maintains event detectionengine code for execution by the master node processing unit. As suchand when executing this event detection engine code, the master nodeprocessing unit is programmatically transformed to becomeunconventionally operative, as part of the system, to use the firstcommunication interface to detect a first set of advertising signalsbroadcast by a first of the ID nodes over the first communication path;generate a first checkpoint summary representing the detected first setof advertising signals; use the first communication interface to detecta second set of advertising signals broadcast by the first ID node overthe first communication path after the first ID node broadcasts thefirst set of advertising signals; and generate a second checkpointsummary representing the detected second set of advertising signalsdetected by the first communication interface. The master nodeprocessing unit is then further operative to compare an observedparameter for each of the first checkpoint summary and the secondcheckpoint summary, identify the event candidate based upon thecomparison of the observed parameter for each of the first checkpointsummary and the second checkpoint summary, and cause the secondcommunication interface to report the identified event candidate to theserver over the second communication path. The system's server is thenresponsively operative to receive the identified event candidate fromthe master node and transmit a responsive adjustment response to themaster node based upon the identified event candidate. Such a responsiveadjustment response comprises at least one of an adjusted profile forthe master node, an adjusted profile for the ID node, and/or updatedcontext data reflecting the identified event candidate.

In another aspect of the disclosure, a master node apparatus (similar tothe system's master node element) is described for enhanced checkpointsummary based monitoring for an event candidate within a wireless nodenetwork having multiple ID nodes and a server. The master node generallyhas a node processing unit (such as a processor or processor-basedcontroller), a memory storage, and two different communicationinterfaces. Each of the memory storage and the communication interfacesare coupled to the node processing unit. A first of the communicationinterfaces is configured and operative to communicate with at least oneof the ID nodes over a first communication path where the secondcommunication interface is configured and operative to communicate withthe server over a second communication path, which is different from thefirst communication path. Thus, the master node apparatus' communicationinterfaces provide separate access to distinct and differentcommunication paths to different elements of the wireless node network(e.g., the server and the ID nodes).

Furthermore, the memory storage maintains event detection engine codefor execution by the node processing unit of the master node apparatus.As such and when executing this event detection engine code, theapparatus' node processing unit is programmatically transformed tobecome unconventionally operative and configured to detect (via thefirst communication interface) a first set of advertising signalsbroadcast by a first of the ID nodes and generate a first checkpointsummary representing the detected first set of advertising signals;detect (via the first communication interface) a second set ofadvertising signals broadcast by the first ID node after the first IDnode broadcasts the first set of advertising signals and then generate asecond checkpoint summary representing the detected second set ofadvertising signals; compare an observed parameter for each of the firstcheckpoint summary and the second checkpoint summary; identify the eventcandidate based upon the comparison of the observed parameter for eachof the first checkpoint summary and the second checkpoint summary; andcause the second communication interface to report the identified eventcandidate to the server over the second communication path.

In still another aspect of the disclosure, a master node-implementedmethod is described for enhanced monitoring for an event candidatewithin a wireless node network having a plurality of ID nodes, a masternode in communication with the ID nodes, and a server in communicationwith the master node. In general, the method begins with the master nodereceiving a first set of advertising signals broadcast by a first of theID nodes and generating a first checkpoint summary representing thereceived first set of advertising signals. The method continues with themaster node receiving a second set of advertising signals broadcast bythe first ID node after the first ID node broadcasts the first set ofadvertising signals and then generating a second checkpoint summaryrepresenting the received second set of advertising signals. The methodproceeds with the master node identifying the event candidate based upona comparison of an observed parameter for each of the first checkpointsummary and the second checkpoint summary, and then reporting, by themaster node to the server, the event candidate relative to the first IDnode.

Each of these aspects respectively effect improvements to the technologyof server-managed networks of wireless nodes that may, for example, bedeployed in logistics applications where nodes are intermediatelymonitored and tracked by various elements of a wireless node network(such as a master node) such that the intermediate element can morequickly and efficiently operate while monitoring and reportingsignificant node-related events up to the managing server for thewireless node network. Additional advantages of this and other aspectsof the disclosed embodiments and examples will be set forth in part inthe description which follows, and in part will be obvious from thedescription, or may be learned by practice of the invention. It is to beunderstood that both the foregoing general description and the followingdetailed description are exemplary and explanatory only and are notrestrictive of the invention, as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments according toone or more principles of the invention and together with thedescription, serve to explain one or more principles of the invention.In the drawings,

FIG. 1 is a diagram of an exemplary wireless node network in accordancewith an embodiment of the invention;

FIG. 2 is a more detailed diagram of an exemplary wireless node networkin accordance with an embodiment of the invention;

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention;

FIG. 4 is a more detailed diagram of an exemplary master node device inaccordance with an embodiment of the invention;

FIG. 5 is a more detailed diagram of an exemplary server in accordancewith an embodiment of the invention;

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention;

FIG. 8 is a state diagram illustrating exemplary states and transitionsbetween the states as part of operations by an exemplary node in awireless node network in accordance with an embodiment of the invention;

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment of the invention;

FIG. 10 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-ID node association in accordancewith an embodiment of the invention;

FIG. 11 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary ID-to-master node query in accordancewith an embodiment of the invention;

FIG. 12 is a diagram illustrating exemplary components of a wirelessnode network during an exemplary alert advertising mode in accordancewith an embodiment of the invention;

FIG. 13 is a diagram illustrating an exemplary location determinationusing master node advertise in accordance with an embodiment of theinvention;

FIG. 14 is a diagram illustrating an exemplary location determinationusing ID node advertise in accordance with an embodiment of theinvention;

FIG. 15 is a diagram illustrating an exemplary location determinationthrough triangulation in accordance with an embodiment of the invention;

FIG. 16 is a diagram illustrating an exemplary location determinationthrough chaining triangulation in accordance with an embodiment of theinvention;

FIG. 17 is a diagram illustrating an example logistics operation usingexemplary components of a wireless node network in accordance with anembodiment of the invention;

FIG. 18 is a flow diagram illustrating an example method for managingshipment of an item using a wireless node network in accordance with anembodiment of the invention;

FIG. 19 is a flow diagram illustrating another example method formanaging shipment of an item using a wireless node network in accordancewith an embodiment of the invention;

FIG. 20 is a diagram illustrating exemplary node packages located in anexemplary vehicle environment in accordance with an embodiment of theinvention;

FIG. 21 is a diagram illustrating exemplary mobile storage units, suchas ULDs, used as containers that help ship node packages in an exemplaryairborne environment in accordance with an embodiment of the invention;

FIGS. 22A-22C are diagrams illustrating exemplary stages of an ID nodemoving through part of an exemplary transit path while associating withdifferent master nodes in accordance with an embodiment of theinvention;

FIG. 23 is a flow diagram illustrating an example method for associationmanagement of a wireless node network in accordance with an embodimentof the invention;

FIG. 24 is a flow diagram illustrating another example method forassociation management of a wireless node network in accordance with anembodiment of the invention;

FIG. 25 is a flow diagram illustrating yet another example method forassociation management of a wireless node network in accordance with anembodiment of the invention;

FIG. 26 is a flow diagram illustrating an exemplary method for contextmanagement of a wireless node network in accordance with an embodimentof the invention;

FIG. 27 is a flow diagram illustrating an exemplary method for locatinga node in a wireless node network based upon observed signal patternsand characteristic indications over a period of time in accordance withan embodiment of the invention;

FIG. 28 is a flow diagram illustrating an exemplary method for locationdetermination by varying a power characteristic of nodes in a wirelessnode network in accordance with an embodiment of the invention;

FIG. 29 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention;

FIG. 30 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 31 is a flow diagram illustrating yet another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention;

FIG. 32 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention;

FIG. 33 is a flow diagram illustrating an exemplary method fordetermining a location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention;

FIG. 34 is a diagram of an exemplary wireless node network that providesevent detection and event candidate processing characterization inaccordance with an embodiment of the invention;

FIG. 35 is a more detailed diagram of another exemplary master node inthe network illustrated in FIG. 34 that operates to monitor for an eventcandidate in accordance with an embodiment of the invention;

FIG. 36 is a more detailed diagram of another exemplary server in thenetwork illustrated in FIG. 34 that operates to receive an eventcandidate and manage the network based upon the event candidate inaccordance with an embodiment of the invention;

FIGS. 37A-37M are a series of graph illustrations that show an exemplarytimeline of detected signals and identified different types of exemplaryevent candidates over time in accordance with an embodiment of theinvention;

FIG. 38 is a flow diagram illustrating an exemplary method formonitoring for an event candidate within a wireless node network basedupon receipt of a first and second advertising signal broadcast by an IDnode in accordance with an embodiment of the invention;

FIG. 39 is a flow diagram illustrating an exemplary method formonitoring for an event candidate within a wireless node network basedupon receipt of a plurality of advertising signals broadcast by an IDnode over time in accordance with an embodiment of the invention;

FIG. 40 is a flow diagram illustrating an exemplary method for enhancedmonitoring for an event candidate within a wireless node network basedupon receipt of a plurality of signals from an ID node and detecting aplurality of time gaps between suggestive ones of the signals inaccordance with an embodiment of the invention;

FIG. 41 is a flow diagram illustrating an exemplary method for enhancedmonitoring for an event candidate within a wireless node network basedupon receipt of a plurality of signals from an ID node and detecting ifthe ID node is broadcasting with a cycling broadcast RF power profilesetting in accordance with an embodiment of the invention;

FIGS. 42A-D are detailed flow diagrams illustrating parts of anexemplary method for enhanced monitoring for an event candidate within awireless node network in accordance with an embodiment of the invention;

FIG. 43 is a flow diagram illustrating an exemplary method for enhancedmanagement of a wireless node network based upon receipt of andprocessing of an event candidate in accordance with an embodiment of theinvention;

FIG. 44 is a flow diagram illustrating another exemplary method forenhanced management of a wireless node network based upon receipt of andprocessing of an event candidate in accordance with an embodiment of theinvention;

FIG. 45 is a flow diagram illustrating an exemplary method for enhancedmonitoring for an event candidate within a wireless node network basedupon checkpoint summary points representing groups or sets of detectedsignals in accordance with an embodiment of the invention; and

FIG. 46 is a flow diagram illustrating another exemplary method forenhanced monitoring for an event candidate within a wireless nodenetwork based upon a checkpoint summary in accordance with an embodimentof the invention.

DESCRIPTION OF THE EMBODIMENTS

Reference will now be made in detail to exemplary embodiments. Whereverpossible, the same reference numbers are used in the drawings and thedescription to refer to the same or like parts.

In general, the following describes various embodiments of acontextually aware hierarchical wireless node network that may bemanaged, operated, and applied by principles as set forth herein. Ingeneral, embodiments of the wireless node network may include one ormore lower level devices or nodes (e.g., an ID node) that rely onshorter-range communication with a higher level device or node (e.g., amaster node), which is operative to communicate with a server over adifferent communication path while the lower level node is unable tocommunicate directly with the server. Those skilled in the art willappreciate that such a hierarchy of different functional communicatingnetwork components (generally referred to as network devices) may becharacterized as a network of nodes. Those skilled in the art willappreciate that in some embodiments, the wireless node network mayinclude the server as well as different wireless nodes despite the factthat the server may not be a dedicated wireless component. In otherembodiments, the network may include similar types of wireless nodes ordifferent types of wireless nodes.

Further, those skilled in the art will appreciate that each embodimentdescribed herein effects improvements to particular technologies, suchas monitoring and node management technologies using an adaptive,context-aware wireless node network of node elements. Each embodimentdescribes a specific technological application of one or more nodes thatoperate in such a wireless node network where the specific technologicalapplication improves or otherwise enhances such technical fields asexplained and supported by the disclosure that follows.

Those skilled in the art will understand through the following detaileddescription that the nodes may be associated with items (e.g., anobject, a package, a person, a piece of equipment) and may be used toidentify and locate the items while being dynamically programmed duringoperation of the network and while the items move along an anticipatedpath (e.g., a transit path from an origin point to a destination point).The following further describes various embodiments of a wireless nodenetwork, exemplary ways to manage components of a wireless node network,exemplary ways to better determine the location of components of awireless node network, and applications of a wireless node network toenhance logistics operations that rely upon a wireless node network. Inparticular, FIGS. 1-33 provide diagrams and flowcharts on basicoperations of various types of network elements deployed within anembodiment of the wireless node network while FIGS. 34-44 provide moredetails regarding embodiments of systems, apparatus and methods forenhanced monitoring for an event candidate related to elements of awireless node network and adaptive management of the wireless nodenetwork based upon the event candidate.

Wireless Node Networks

FIG. 1 illustrates a basic diagram of an exemplary wireless node networkin accordance with an embodiment of the invention. The exemplary networkshown in FIG. 1 comprises a server 100 connected to a network 105, whichis also operatively connected to different network components, such as amaster node 110 a and indirectly to an ID node 120 a through master node110 a. Master node 110 a is typically connected to an ID node 120 a viashort-range wireless communications (e.g., Bluetooth® formattedcommunications). Master node 110 a is typically connected to server 100through network 105 via longer-range wireless communication (e.g.,cellular) and/or medium range wireless communication (e.g., wirelesslocal area data networks or Wi-Fi). ID node 120 a is typically a lowcost device that may be easily placed into a package, be integrated aspart of packaging, or otherwise associated with an item to be trackedand located, such as package 130, a person, or object (e.g., vehicle,etc.). Generally, an ID node is capable of communicating directly with amaster node but incapable of communicating directly with the server,while a master node is capable of communicating directly with the serverand separately and directly communicating with other nodes (such as anID node or another master node). The ability to deploy a hierarchy ofnodes within an exemplary wireless node network to distribute tasks andfunctions at the different levels in an efficient and economical mannerhelps to facilitate a wide variety of adaptive locating, tracking,managing, and reporting applications using such a network of nodes asdiscussed in more detail below.

In general, the lower cost, lower complexity ID node 120 a is managed bythe higher complexity master node 110 a and server 100 as part ofkeeping track of the location of ID node 120 a (and the associateditem), thereby providing intelligent, robust, and broad visibility aboutthe location and status of ID node 120 a. In a typical embodiment, IDnode 120 a is first associated with an item (e.g., package 130, aperson, or object). As ID node 120 a moves with the item, the ID node120 a becomes associated with the master node 110 a, and the server 100is updated with such information. Further movement of the ID node 120 aand item may cause the ID node 120 a to disassociate with master node110 a and be handed off to become associated another master node (notshown), after which the server 100 is again updated. As such, the server100 generally operates to coordinate and manage information related tothe ID node 120 a as the item physically moves from one location toanother. Further details of the architecture and functionality of anembodiment of an exemplary ID node and master node as described below inmore detail with respect to FIGS. 3 and 4, while exemplary server 100 isdescribed below in more detail with respect to FIG. 5.

While server 100 is shown connecting through network 105, those skilledin the art will appreciate that server 100 may have a more direct ordedicated connections to other components illustrated in FIG. 1, such asmaster node 110 a, depending upon implementation details and desiredcommunication paths. Furthermore, those skilled in the art willappreciate that an exemplary server may contain a collection ofinformation in a database (not shown in FIG. 1), while multipledatabases maintained on multiple server platforms or network storageservers may be used in other embodiments to maintain such a collectionof information. Furthermore, those skilled in the art will appreciatethat a database may be implemented with cloud technology thatessentially provides networked storage of collections of informationthat may be directly accessible to devices, such as master node 110 a.

Network 105 may be a general data communication network involving avariety of communication networks or paths. Those skilled in the artwill appreciate that such exemplary networks or paths may be implementedwith hard wired structures (e.g., LAN, WAN, telecommunication lines,telecommunication support structures and telecommunication processingequipment, etc.), wireless structures (e.g., antennas, receivers,modems, routers, repeaters, etc.) and/or a combination of both dependingupon the desired implementation of a network that interconnects server100 and other components shown in FIG. 1 in an embodiment of the presentinvention.

Master node 110 a and ID node 120 a are types of nodes. A node isgenerally an apparatus or device used to perform one or more tasks aspart of a network of components. An embodiment of a node may have aunique identifier, such as a Media Access Control (MAC) address or anaddress assigned to a hardware radio like an Internet Protocol 6 (IPv6)identifier. In some embodiments, the node's unique identifier may becorrelated to a shipment identifier (e.g., a shipment tracking number inone example), or may itself be a shipment's tracking reference.

An ID node, such as ID node 120 a, is generally a low cost activewireless device. In one embodiment, an exemplary ID node is atransceiver-based processing or logic unit having a short-range radiowith variable RF characteristics (e.g., programmable RF output powerrange, programmable receiver sensitivity), memory accessible by theprocessing unit, a timer operatively coupled to the processing unit, anda power source (e.g., a battery) that provides power for the circuitryof the ID node. For example, the physical implementation of an exemplaryID node may be small, and, thus, amenable to integration into a package,label, container, or other type of object. In some implementations of anID node, the node is rechargeable while other implementations do notpermit recharging the power source for the ID node. In otherimplementations, the ID node is environmentally self-contained or sealedso as to enable robust and reliable operations in a variety ofenvironmentally harsh conditions.

A master node, such as master node 110 a, generally serves as anintelligent bridge between the ID node 120 a and the server 100.Accordingly, a master node is generally more sophisticated than an IDnode. In one example embodiment, an exemplary master node is a devicehaving a processing or logic unit, a short-range radio (with may havevariable RF characteristics) used for communicating with other nodes (IDnodes and other master nodes), a medium and/or long-range radio forcommunication with the server 100, memory accessible by the processingunit, a timer operatively coupled to the processing unit, and a powersource (e.g., a battery or a wired power supply connection) thatprovides power for the circuitry of the master node. The exemplarymaster node, such as master node 110 a, may be positioned in a knownfixed location or, alternatively, be a mobile unit having dedicatedlocation positioning circuitry (e.g., GPS circuitry) to allow the masternode to determine its location by itself.

While the embodiment illustrated in FIG. 1 shows only a single masternode and a single ID node, those skilled in the art will appreciate thata wireless network consistent with an embodiment of the invention mayinclude a wide array of similar or different master nodes that eachcommunicate with the server 100 and/or other master nodes, and a widevariety of similar or different ID nodes. Thus, the exemplary networkshown in FIG. 1 is a basic embodiment, while the exemplary network shownin FIG. 2 is a more detailed exemplary wireless node network inaccordance with another embodiment of the invention.

Referring now to FIG. 2, another exemplary wireless node network isshown including server 100 and network 105. Here, master nodes 110 a,110 b, 110 c are deployed and connected to network 105 (and by virtue ofthose respective connections, to server 100) as well as to each other.ID nodes 120 a, 120 b, 120 e are shown as connectable or operative tocommunicate via different paths to various master nodes. However, IDnodes 120 c and 120 d are shown in FIG. 2 connected to ID node 120 b butnot to any of the master nodes. This may be the case if, for example, IDnodes 120 b, 120 c, 120 d are associated with different items (e.g.,packages) within a larger container 210 (or grouped together on apallet). In such an example, only ID node 120 b may remain within thewireless communication range of any master node. This may, for example,be because of the positions of the different ID nodes within thecontainer relative to the closest master node, adverse RF shieldingcaused by the container, adverse RF shielding caused by packaging of theitem, or adverse RF shielding caused by other proximate material thatinterferes with radio transmissions (e.g., several packages of metalitems between the ID node and any master node outside the container).Thus, in the illustrated configuration of the exemplary network shown inFIG. 2, ID nodes 120 c and 120 d may be out of range from the masternodes, yet still have an operative communication path to a master nodethrough ID node 120 b.

Indeed, in one example, prior to placement within container 210, ID node120 b may actually be a master node but the changed RF environment whenplacing it in container 210 may interfere with the master node's abilityto locate itself via location signals (e.g., GPS signals) and cause themaster node to temporarily operate as an ID node while still providingcommunications and data sharing with other ID nodes in container 210.

User access devices 200, 205 are also illustrated in FIG. 2 as beingable to connect to network 105, master nodes, and ID nodes. Generally,user access devices 200 and 205 allow a user to interact with one ormore components of the exemplary wireless node network. In variousembodiments, user access devices 200, 205, may be implemented using adesktop computer, a laptop computer, a tablet (such as an Apple iPad®touchscreen tablet), a personal area network device (such as aBluetooth® device), a smartphone (such as an Apple iPhone®), a smartwearable device (such as a Samsung Galaxy Gear™ smartwatch device, or aGoogle Glass™ wearable smart optics) or other such devices capable ofcommunicating over network 105 with server 100, over a wired or wirelesscommunication path to master node and ID nodes. Thus, an exemplary useraccess device may be a mobile type of device intended to be easily moved(such as a tablet or smartphone), and may be a non-mobile type of deviceintended to be operated from a fixed location (such as a desktopcomputer).

As shown in FIG. 2, user access devices 200, 205 are coupled and incommunication with network 105, but each of them may also be incommunication with each other or other network components in a moredirect manner (e.g., via near field communication (NFC), over aBluetooth® wireless connection, over a Wi-Fi network, dedicated wiredconnection, or other communication path).

In one example, a user access device, such as device 200 or 205, mayfacilitate associating an ID node (such as ID node 120 a) with thetracking number of a package at the start of a shipment process,coordinating with the server 100 to check on the status and/or locationof the package and associated ID node during transit, and possiblyretrieving data from a master node or ID node related to the shippedpackage. Thus, those skilled in the art will appreciate that a useraccess device, such as devices 200, 205, are essentially interactivecommunication platforms by which a user may initiate shipment of anitem, track an item, determine the status and location of an item, andretrieve information about an item.

An exemplary user access device, such as device 200 or 205, may includesufficient hardware and code (e.g., an app or other program code sectionor sections) to operate as a master node or an ID node in variousembodiments as discussed in more detail below. For example, device 200may be implemented as a mobile smartphone and functionally may operateas an exemplary ID node that broadcasts advertising packet messages toother ID nodes or master nodes for association and sharing data withsuch nodes. In another example, device 200 is implemented as a mobilesmartphone and may operate as an exemplary master node that communicatesand associates with ID nodes and other master nodes, as describedherein, and communicates with the server 100. Thus, those skilled in theart will appreciate an exemplary ID node in FIG. 3 and an exemplarymaster node in FIG. 4, and their respective parts, code and programmodules, may be implemented with an appropriately programmed user accessdevice, such as device 200 or 205. Thus, the following description of anexemplary ID node in FIG. 3 and an exemplary master node in FIG. 4 willbe applicable to a user access device operating as an ID node or amaster node, respectively.

ID Node

FIG. 3 is a more detailed diagram of an exemplary ID node device inaccordance with an embodiment of the invention. As previously described,one embodiment of an ID node includes a transceiver-based processing orlogic unit having a short-range radio with variable RF characteristics(e.g., programmable RF output power range, programmable receiversensitivity), memory accessible by the processing unit, a timeroperatively coupled to the processing unit, and a power source (e.g., abattery) that provides power for the circuitry of the ID node. Referringnow to the more detailed embodiment of FIG. 3, exemplary ID node 120 ais shown to comprise a processing or logic unit 300 coupled to avariable power short-range communication interface 375, memory storage315, volatile memory 320, timer 370, and battery 355. Those skilled inthe art will appreciate that processing unit 300 is logic, such as a lowpower consumption microcontroller, that generally performs computationson data and executes operational and application program code and otherprogram modules or sections thereof within the ID node 120 a. As such,exemplary processing unit 300 operates as a transceiver-based processingcore of ID node 120 a.

Those skilled in the art will also appreciate that exemplary ID node 120a is a hardware-based component that may be implemented with a singleprocessor or logic unit, such as unit 300. In one embodiment, processingunit 300 may be implemented with an Intel® 8051 CPU Core and associatedperipheral circuitry as dictated by the needs of the particularapplication. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 300 as well as more complex andsophisticated microprocessors. Additionally, exemplary processing unit300 may be integrated into a single chip transceiver used as a core ofID node 120 a.

The variable power short-range communication interface 375 of ID node120 a is generally a programmable radio and an omni-directional antennacoupled to the processing unit 300. In other embodiments, interface 375may use an antenna with a different antenna profile when directionalitymay be desired. Examples of variable power short-range communicationinterface 375 may include other interfacing hardware (not shown) foroperatively coupling the device to a specific short-range communicationpath (e.g., a Bluetooth® Low Energy (BLE) connection path communicatingat 2.4 GHz).

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and/or the RF receiversensitivity may be dynamically and programmatically varied under controlof processing unit 300. In other embodiments, further RF characteristicsof the radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal depending upon a desired implementation and anticipateduse of ID node 120 a. As will be explained in more detail below, someembodiments may use Broadcast Profile having parameters that may beprogrammatically altered or adjusted. In other words, embodiments of IDnode 120 a (or any other ID node) may have programmatically adjustableRF characteristics (such as an adjustable RF output signal power, anadjustable RF receiver sensitivity, the ability to switch to a differentfrequency or frequency band, etc.).

The battery 355 for ID node 120 a is a type of power source thatgenerally powers the circuitry implementing ID node 120 a. In oneembodiment, battery 355 may be a rechargeable power source. In otherembodiments, battery 355 may be a non-rechargeable power source intendedto be disposed of after use. In some embodiments of an ID node, thepower source may involve alternative energy generation, such as a solarcell.

The timer 370 for ID node 120 a generally provides one or more timingcircuits used in, for example, time delay, pulse generation, andoscillator applications. In an embodiment where ID node 120 a conservespower by entering a sleep or dormant state for a predetermined timeperiod as part of overall power conservation techniques, timer 370assists processing unit 300 in managing timing operations. Additionally,an embodiment may allow an ID node to share data to synchronizedifferent nodes with respect to timer 370 and a common timing referencebetween nodes and the server.

An embodiment may implement ID node 120 a to optionally include a basicuser interface (UI) 305 indicating status and allowing basic interactionlike start/stop. In one embodiment, the UI 305 may be implemented withstatus lights, such as multi-mode LEDs. Different colors of the lightsmay indicate a different status or mode for the ID node 120 a (e.g., anadvertising mode (broadcasting), a scanning mode (listening), a currentpower status, a battery level status, an association status, an error,as sensed condition (e.g., exceeding a temperature threshold, exceedinga moisture threshold, and the like)). Other embodiments of an ID nodemay implement U! 305 in a more sophisticated manner with a graphicsdisplay or the like where such status or mode information may bedisplayed as well as one or more prompts.

In a further embodiment, an exemplary status light used as part of theUI 305 of an ID node may also indicate a shipment state. In more detail,an exemplary shipment state may include a status of the shipped item ora status of the item's current shipment journey from an origin to adestination.

An embodiment may also implement ID node 120 a to optionally include oneor more sensors 360. In some embodiments, an ID node implemented withone or more sensors 360 may be referred to as a Sensor node. Examples ofsensor 360 may include one or more environmental sensors (e.g.,pressure, movement, light, temperature, humidity, magnetic field,altitude, attitude, orientation, acceleration, etc.) and dedicatedlocation sensors (e.g., GPS sensor, IR sensor, proximity sensor, etc.).Those skilled in the art will understand that additional types ofsensors that measure other characteristics are contemplated for use assensor 360. Additionally, those skilled in the art will understand thata Sensor node may include additional program features to manage thecollection, storage, sharing, and publication of the captured sensordata.

An embodiment may further implement ID node 120 a to optionally includeone or more magnetic switches 365. A magnetic switch 365, such as a reedswitch, generally operates to close or open an electrical path orconnection in response to an applied magnetic field. In other words,magnetic switch 365 is actuated by the presence of a magnetic field orthe removal of a magnetic field. Various applications, as discussed inembodiments described in more detail below, may involve the operation ofID node 120 a having magnetic switch 365.

Consistent with the embodiment shown in FIG. 3, exemplary ID node 120 amay be implemented based upon a Texas Instruments CC2540 Bluetooth® LowEnergy (BLE) System-on-Chip, which includes various peripherals (e.g.,timer circuitry, USB, USART, general-purpose I/O pins, IR interfacecircuitry, DMA circuitry) to operate as an ID node and, if necessary, tointerface with different possible sensors and other circuitry (e.g.,additional logic chips, relays, magnetic switches) that make up the IDnode.

In additional embodiments, one skilled in the art will appreciate thatsimilar functionality in an ID node may be implemented in other types ofhardware. For example, ID node 110 a may be implemented with speciallyoptimized hardware (e.g., a particular application specific integratedcircuit (ASIC) having the same operational control and functionality asnode control and management code, as described below, discrete logic, ora combination of hardware and firmware depending upon requirements ofthe ID node, such as power, processing speed, level of adjustability forthe RF characteristics, number of memory storage units coupled to theprocessor(s), cost, space, etc.

As noted above, ID node 120 a includes memory accessible by theprocessing unit 300. Memory storage 315 and volatile memory 320 are eachoperatively coupled to processing unit 300. Both memory componentsprovide programming and data elements used by processing unit 300. Inthe embodiment shown in FIG. 3, memory storage 315 maintains a varietyof program code (e.g., node control and management code 325) and otherdata elements (e.g., profile data 330, security data 335, associationdata 340, shared data 345, sensor data 350, and the like). Memorystorage 315 is a tangible, non-transient computer readable medium onwhich information (e.g., executable code/modules, node data, sensormeasurements, etc.) may be kept in a non-volatile and non-transitorymanner. Examples of such memory storage 315 may include a hard diskdrive, ROM, flash memory, or other media structure that allows longterm, non-volatile storage of information. In contrast, volatile memory320 is typically a random access memory (RAM) structure used byprocessing unit 300 during operation of the ID node 120 a. Upon power upof ID node 120 a, volatile memory 320 may be populated with anoperational program (such as node control and management code 325) orspecific program modules that help facilitate particular operations ofID node 120 a. And during operation of ID node 120 a, volatile memory320 may also include certain data (e.g., profile data 330, security data335, association data 340, shared data 345, sensor data 350, and thelike) generated as the ID node 120 a executes instructions as programmedor loaded from memory storage 315. However, those skilled in the artwill appreciate that not all data elements illustrated in FIG. 3 mustappear in memory storage 315 and volatile memory 320 at the same time.

Node Control & Management Code

Generally, an embodiment of node control and management code 325 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a node, such asID node 120 a. In an embodiment, the functionality of code 325 may begenerally similar as implemented in different types of nodes, such as amaster node, an ID node, and a sensor node. However, those skilled inthe art will appreciate that while some principles of operation aresimilar between such nodes, other embodiments may implement thefunctionality with some degree of specialization or in a differentmanner depending on the desired application and use of the node.

In a general embodiment, exemplary node control and management code 325may generally comprise several programmatic functions or program modulesincluding (1) a node advertise and query (scan) logic manager (alsoreferred to herein as a node communications manager), which manages howand when a node communicates; (2) an information control and exchangemanager, which manages whether and how information may be exchangedbetween nodes; (3) a node power manager, which manages power consumptionand aspects of RF output signal power and/or receiver sensitivity forvariable short-range communications; and (4) an association managerfocusing on how the node associates with other nodes. What follows isdescription of various embodiments of these basic program modules usedby nodes.

Node Communications Manager—Advertising & Scanning

In an exemplary embodiment, the node advertise and query (scan) logicmanager governs how and when a node should advertise (transmit) itsaddress or query (scan) for the address of neighboring nodes.Advertising is generally done with a message, which may have differentinformation in various parts (e.g., headers, fields, flags, etc.). Themessage may be a single or multiple packets.

In the exemplary embodiment, the “advertise” mode (as opposed to “query”or “scan” mode) is a default mode for an ID Node and has the nodebroadcasting or transmitting a message with its address and relatedmetadata regarding the node. For example, in one embodiment, exemplarymetadata may include information such as the RF output power level, areference number, a status flag, a battery level, and a manufacturername for the node.

FIG. 6 is a diagram illustrating the structure or format of an exemplaryadvertisement data packet in accordance with a general embodiment of theinvention. Referring now to FIG. 6, the structure of an exemplaryadvertisement data packet 600 broadcast as a signal or message from anID node, such as ID node 120 a, is shown. Packet 600 appears with anincreasing level of detail showing exemplary metadata and a format thatseparately maintains distinct types of metadata in different parts ofthe packet. Different embodiments may include different types ofmetadata depending on the deployed application of the ID node.

FIG. 7 is a diagram illustrating sample content for an exemplaryadvertisement data packet in accordance with an embodiment of theinvention. Referring now to FIG. 7, an exemplary advertisement datapacket 700 is illustrated with exemplary metadata including showingsample information such as the RF Output Power level (e.g., “TX PowerLevel”), a reference number (e.g., “‘FDX ID’ (ASCII Short Name)”, astatus flag (e.g., “Status Flag Value (indicates ‘Ack Requested’)”), abattery level (e.g., “Battery Level Value (Indicates 73% charge)”, and amanufacturer name for the node (e.g., “Company Identifier (currentlyundefined for FedEx)”). In one embodiment, those skilled in the art willappreciate that the reference number may be omitted or obfuscated forsecurity purposes.

In one embodiment, an exemplary advertising data packet may include theRF Output power level, as noted above in FIG. 7, to enable one way tohelp identify the type of node doing the broadcasting and the locationof the broadcasting node. However, if the broadcast RF output powerlevel is fixed and known by the node type, only the node type need beidentifiable from an exemplary advertising data packet, such as packet700.

Regarding how a node communicates, an exemplary node may be in one ofseveral different communication modes. A node in an advertising (ortransmit or broadcast) mode is visible to any other node set in a query(or scan or listen) mode. In an embodiment, the frequency and length ofadvertising may be application and power dependent. For example, innormal operations, an exemplary node will generally advertise in aperiodic manner and expect to make an active connection to another nodeat certain intervals, which may be dictated by conditions set by server100. In an embodiment, such conditions may be set individually for anode by the server or a higher level node in the network.

If an exemplary node has not received acknowledgement for an advertisingpacket within a particular period, it may enter one or more alertstages. For example, if an exemplary node has not receivedacknowledgement from another node for an advertising packet broadcast bythe exemplary node within a particular time period (also generallyreferred to as an Alert Interval), the exemplary node will enter anAlert Stage 1 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 1 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has not received acknowledgement from a master nodefor an advertising packet broadcast by the exemplary node within anothertime period (e.g., a request from the master node to actively connectand a success connection made), it will enter another alert stage, suchas an Alert Stage 2 status. This prompts the exemplary node to issue afollow-up advertising packet having one or more parts of it altered toindicate the Alert Stage 2 status. In more detail, this exemplaryfollow-up advertising packet may have a different advertising alertheader instructing nearby master nodes to send a SCAN_REQ message uponreceiving an advertisement packet.

If an exemplary node has data to upload to the backend, it may alsoenter another type of alert stage. In one embodiment, for example, if anexemplary node has sensor data collected by the exemplary node (orreceived from one or more other nodes that have communicated with theexemplary node), and the data needs to be uploaded to server 100, theexemplary node may enter an update alert stage, such as an Alert Stage3. This prompts the exemplary node to issue a follow-up advertisingpacket having one or more parts of it altered to indicate the AlertStage 3 status. In more detail, this exemplary follow-up advertisingpacket may have a different advertising alert header instructing nearbymaster nodes to make a connection with the exemplary node so that thedata (e.g., sensor data 350) may be transmitted from the exemplary node(e.g., ID node 120 a) to a nearby master node (e.g., master node 110 a).The transmitted data may then be stored by the nearby master node assensor data 450 in either or both of the master node's volatile memory420 and memory storage 415. Subsequent to that storage operation, thenearby master node will transfer the data (e.g., sensor data 450) toserver 100.

As illustrated in FIG. 7 and explained in the above description of alertlevel stages, a status flag in a header of an exemplary advertising datapacket is a field used in the association logic in one or moreembodiments. For example, in one embodiment, the existence of a statusflag in the advertising data packet allows a first node to communicateits status to a second node, and for the second node to report thatstatus to the backend server, such as server 100, without an activedirect connection from the first node to the server. In other words, thestatus flag helps facilitate passive interactions between nodes (such aspassive associations).

In a more detailed embodiment, several exemplary status types areestablished with respect to communications with other nodes. Forexample, the exemplary status types may comprise the following:

-   -   Alert Level 0—no issue, operating normal;    -   Alert Level 1—The advertising node is requesting that any        available node acknowledge the receipt of its advertisement        packet;    -   Alert Level 2—The advertising node is requesting that any        available master node acknowledge the receipt of its        advertisement packet;    -   Alert Level 3—Data for Upload—node has captured data available        for upload through a master node; and    -   Synchronize—The advertising node requests to connect with a        device or sensor that can synchronize data (such as timer or        location information).

By broadcasting the status via, for example, a portion of a header in anadvertising data packet, one or more nodes within range of thebroadcasting node can determine the node's status and initiate activeconnections if requested in the status message.

A request for more information from the advertising node may, in someembodiments, come in the form of a SCAN_REQ message. In general, anexemplary SCAN_REQ is a message sent from a scanning (listening) masternode to an advertising node requesting additional information from theadvertising node. In this example, the alert status bit may indicate tothe scanning master node, for example, at an application layer, whetherthe advertising node is in a mode that will or will not accept aSCAN_REQ. In one embodiment, the non-connectable and discoverable modesof node advertising are in compliance with Bluetooth® Low Energy (BLE)standards.

In another embodiment, a node may have further different modes ofoperation while scanning or listening for other nodes. For example, anode's query or scanning mode may be active or passive. When a node isscanning while passive, the node will receive advertising data packets,but will not acknowledge and send SCAN_REQ. However, when a node isscanning while active, the node will receive advertising data packets,and will acknowledge receipt by sending a SCAN_REQ. A more detailedembodiment may provide the passive and active modes of scanning orinquiry in compliance with Bluetooth® Low Energy (BLE) standards.

In an embodiment, an exemplary node is scanning as it listens for otherwireless nodes broadcasting on the short-range radio. An exemplaryscanning node may capture, for example, a MAC address of the advertisingnode, a signal strength of the RF output signal transmitted from theadvertising node, and any other metadata published by the advertisingnode (e.g., other information in the advertising data packet). Thoseskilled in the art will appreciate that the scope of “listening” when anode is scanning may vary. For example, the query may be limited. Inother words, the scope of what a node is particularly interested in andfor which it is listening may be focused or otherwise limited. In such acase, for example, the information collected may be limited toparticular information from a targeted population of short-rangewireless nodes advertising; but the information collection may beconsidered “open” where information from any advertising device iscollected.

When nodes are advertising or scanning, an embodiment may make furtheruse of status flags and additional modes when advertising or scanning aspart of how nodes communicate and may be managed. In one example, when ascanning (listening) node receives an advertising data packet with thestatus flag indicating an Alert Level 1 or 2 status, and the scanningnode is in “Passive” scanning mode, the node will switch to “Active”scanning mode for some interval. However, when the scanning node in thissituation is already in an “Active” scanning mode, the node will sendthe SCAN_REQ message and receive a SCAN_RSP from the advertising node(e.g., a message providing the additional information requested from theadvertising node). The scanning node will then switch back to a“Passive” scanning mode.

In another example, when an advertising (broadcasting) node receives aSCAN_REQ from a scanning node, the advertising node will consider thatits advertising data packet has been acknowledged. Further, theadvertising node will reset its “Alert” status flag back to an AlertLevel 0 status. This allows the advertising node to effectively receivean acknowledgement to its advertisement without ever making a connectionto the scanning node, which advantageously and significantly saves onpower consumption.

In yet another example, when a scanning node receives an advertisingdata packet with an Alert Level 3 status flag set, the scanning nodewill attempt to make a connection with the advertising device. Once theconnection is made, the advertising device will attempt to upload itsdata to the connected device

Thus, an embodiment of the node advertise and query (scan) logic managerof code 325 may rely upon one or more status flags, advertising modes,scanning modes, as nodes communicate with each other in variousadvantageous manners.

Node Information Control & Exchange Manager

In an exemplary embodiment, the information control and exchange managerpart of node control and management code 325 determines whether and howinformation may be exchanged between nodes. In the exemplary embodiment,the information control and exchange manager establishes different nodeoperational states where information may be changed according to adesired paradigm for the state. In more detail, an embodiment ofinformation control and exchange manager may establish different levelsof information exchange between nodes with a “non-connectableadvertising” state or mode of operation, a “discoverable advertising”state or mode, and a “general advertising” state or mode operation. Whena node is in the “non-connectable advertising” mode, the nodeinformation exchange is limited. For example, the advertising node maybroadcast information that is captured by one or more querying(scanning) nodes, but no two-way exchange of information happens.

When a node is in the “discoverable advertising” mode and a scanningnode is in “Active” mode, the node information exchange in enabled bothways. For example, the advertising node sends the advertising packet,and in response the scanning node sends the SCAN_REQ packet. After theadvertising node receives the SCAN_REQ requesting additionalinformation, the advertising node sends the SCAN_RSP with the requestedinformation. Thus, in the “discoverable advertising” mode there is atwo-way exchange of information, but no active connection is madebetween the two nodes exchanging information.

Finally, for advanced two-way information exchange, an active connectionmay be used between nodes and information may be exchanged both ways toand from different nodes. In a more detailed embodiment, at this levelof two-way information exchange, nodes are first identified and thenauthenticated as part of establishing the active connection. Onceauthenticated and thereafter actively connected to each other, the nodesmay securely share information back and forth. In one example, a sensornode uploading previously captured environmental information to a masternode may be in this mode or state. In another example, an ID nodeuploading the stored results of a node scanning operation to a masternode may be in this mode or state. In yet another example, a master nodesharing a timer and/or location information with corresponding nodes maybe in this mode or state.

Node Power Manager

In an exemplary embodiment, the node power manager part of node controland management code 325 focuses on managing power consumption and theadvantageous use of power (e.g., an adjustable level of RF output signalpower) in a node. In general, nodes are either powered by a battery(such as battery 355 in an ID node), or by an interface (such asbattery/power interface 470 in a master node) to an external powersource. Examples of an external power source may include, in someembodiments, power supplied from an outlet or power connection within afacility, or power generated onboard a conveyance (e.g., automobile,truck, train, aircraft, ship, etc.). Those skilled in the art willappreciate that an interface to an external power source will begenerally referred to as a “wired” power connection, and that node powermanager may be informed whether a node is wired or powered off abattery, such as battery 355. Further embodiments may implement aninterface to an external power source with wireless power transmission,such as via inductive coils.

In one embodiment, a node may manage power used when performing tasks.For example, a node may manage power when determining which node shouldperform a particular task. In more detail, the collective powerconsumption of a group of devices may be managed by electing to employwired nodes, when feasible or desired, to accomplish a particular task,and saving the battery-powered nodes for other less energy burdensome ortaxing tasks. In another embodiment, historic data may inform the systemof the power needed to accomplish a particular task, and the system maymake a determination of which node should accomplish the particular taskbased upon such historic data. In other embodiments, profile data mayalso be used to inform the system of the power needed to accomplish aparticular task (e.g., a sensor profile that describes powerrequirements for operation of a sensor node that gathers sensor dataover a certain period of time and under certain conditions). The systemmay also make a determination of which node should accomplish theparticular task based upon such profile data.

In another example, the exemplary node power manager may manage powerwhen determining how to best to use and adjust power to more accuratelyaccomplish a particular task. In one embodiment, an RF signal outputfrom a node (such as a short-range RF output signal from an ID node) mayperiodically move through a range of output power or simply switchbetween two or more settings that differ in a detectable manner. Asdisclosed in more detail below, the variability and dynamic adjustmentof RF output signal power may allow other nodes (such as one or moremaster nodes) to see each node at the upper range of the RF outputsignal power, and only see nodes physically close to the advertisingnode at the lower range of signal power.

In another example, the exemplary node power manager may cause a changeto a characteristic of its RF output signal power when the node has beenassociated to a physical place or another node by virtue of context data(such as context data 560 and association logic that utilizes that typeof information). In one embodiment, the node may be instructed to changehow often the node communicates and/or a characteristic of its RF outputpower to preserve power.

In yet another example, all advertising nodes may have their respectivenode power managers periodically cause each respective node to broadcastat a maximum RF output signal power level to ensure they still arewithin range of a scanning ID Node or Master Node. Doing so may increasethe chance of being in communication range and allows the individualnodes to be properly located and managed within the network. Thebroadcast duration may be set or dynamically changed to allow pairing tooccur if needed.

Rather than adjust the RF output signal power level, the exemplary nodepower manager may, in some embodiments, adjust the RF receiversensitivity of a node. This allows for an adjustable range of reception(as opposed to merely an adjustable range of broadcast), which maysimilarly be used to manage power and enhance location determinations asdiscussed herein.

In yet another embodiment, a combination approach may be used in whichthe node power manager may concurrently and independently adjust morethan one RF characteristic of a node. For example, an exemplary nodepower manager may adjust an RF output signal power level and also adjustthe RF receiver sensitivity of a node as the node is located andassociated with other nodes. Those skilled in the art will realize thatthis may be especially useful in an area with an unusually denseconcentration of nodes, and a combination of changing RF output signalpower levels

An embodiment of the exemplary node manager may refer to a power profile(e.g., an exemplary type of profile data 330, 430) when adjusting anode's power characteristics (e.g., consumption of power, use of power,output signal frequency, duty cycle of the output put signal, timing,power levels, etc.).

Node Association Manager

In an exemplary embodiment, the node association manager part of nodecontrol and management code 325 focuses on how the nodes associate withother nodes in conjunction and consistent with the server-sideassociation manager in code 525, as discussed in more detail below.Thus, exemplary node association manager, when executing in a node,directs how the node associates (e.g., enters an active connection mode)with one or more other nodes with input from the server.

The exemplary node association manager for a node may indicate through aStatus Flag if the node requires an acknowledgement or connection, or ifit has information available for upload to the backend. Thus, while anode may not be associated or actively connected yet to another node, astatus of the node may be inferred from, for example, the statusinformation in the node's broadcast header.

Regarding connections between nodes, there are generally secureconnections and unsecure connections. While an embodiment may allowunsecure connections between one or more sets of nodes, otherembodiments rely upon secure connections or authenticate pairings ofnodes. In one embodiment, for a node to pair with another node, theexemplary node association manager first identifies the nodes to beassociated and transmits an association request to the server. Therequest may include a specific request to pair the nodes and ask for thecorresponding pairing credentials from the server, such as server 100.The server 100 may have staged pairing credentials on particular nodesbased on information indicating the nodes would be within wirelessproximity and future pairing may occur. Visibility to the noderelationship may have been determined through scan-advertising, or3^(rd) party data such as barcode scan information indicating the nodesto be within proximity currently or at a future state.

When connecting or not connecting to exchange information under theexemplary node information exchange modes described above, nodesgenerally operate in a number of states, which make up an exemplaryadvertise cycle for an exemplary ID node. Such an exemplary advertisecycle for a node is further explained below with reference to FIG. 8 andin conjunction and consistent with the server-side association managerin code 525, as discussed in more detail below.

Airborne Mode Program Module

In one embodiment, node control and management code 325 may also includean airborne mode program module (not shown). In another embodiment, theairborne mode program module may be implemented as a part of the nodepower manager program module of code 325. An exemplary airborne modeprogram module generally operates to manage the output power of the IDnode's variable power short-range communication interface 375 when theID node is operating in an aircraft. Operating a wireless device withinan aircraft may, in some circumstances, have an unintentional impact onother electronic systems on the aircraft. In more detail, an embodimentof the airborne mode program module may operate to transition the IDnode from different states or modes depending upon particular operationsand/or operational conditions of the aircraft. For example, an exemplaryairborne mode program module may operate to transition the ID node fromone state or mode (e.g., a normal mode prior to takeoff, a disabled modeduring takeoff, an airborne mode while aloft, a disabled mode duringdescent, and a normal mode after landing) based upon detectedenvironmental conditions (e.g., pressure, altitude) and/or flight detailinformation associated with the aircraft. In this way, an ID node may beallowed to normally operate when onboard an aircraft, be disabled fromoperating at all in some circumstances, and be able to operate in anairplane mode that allows sensing and sensor data capture, but that maylimit transmission of an RF output signal to avoid interference with theaircraft's onboard electronics. Further information related to a methodof managing a wireless device (such as an ID node) in an aircraft isdisclosed in greater detail in U.S. patent application Ser. No.12/761,963 entitled “System and Method for Management of WirelessDevices Aboard an Aircraft,” which is hereby incorporated by reference.

Node Data

As previously noted, volatile memory 320 may also include certain data(e.g., profile data 330, security data 335, association data 340, shareddata 345, sensor data, and the like) generated as the ID node 120 aexecutes instructions as programmed or loaded from memory storage 315.In general, data used on a node, such as an ID node, may be receivedfrom other nodes or generated by the node during operations.

In one embodiment, profile data 330 is a type of data that defines ageneral type of behavior for an ID node, such as a Broadcast Profile(discussed in more detail below). In another embodiment where ID node120 a is a BLE device, profile data 330 may include a Bluetooth®compatible profile related to battery service (exposing the state of abattery within a device), proximity between BLE devices, or messagingbetween BLE devices. Thus, exemplary profile data 330 may exist involatile memory 320 and/or memory storage 315 as a type of data thatdefines parameters of node behavior.

In one embodiment, it may be desired to allow secured pairings of nodes.As will be explained in more detail below, as part of secure pairing ofnodes, a request for pairing credentials is generated and sent to server100. Thus, exemplary security data 335 (e.g., PIN data, securitycertificates, keys, etc.) may exist in volatile memory 320 and/or memorystorage 315 as a type of data associated with providing securedrelationships between nodes, such as the requested security credentials.

Association data, such as association data 340, generally identifies aconnected relationship between nodes. For example, ID node 120 a maybecome associated with the master node 110 a as the ID node 120 a moveswithin range of the master node 110 a and after the server directs thetwo nodes to associate (with authorization). As a result, informationidentifying the relationship between ID node 120 a and master node 110 amay be provided to server 100 and may be provided, as some point, toeach of ID node 120 a and master node 110 a. Thus, exemplary associationdata 340 may exist in volatile memory 320 and/or memory storage 315 as atype of data identifying associations between nodes.

Shared data 345 may exist in volatile memory 320 and/or memory storage315 as a type of data exchanged between nodes. For example, context data(such as environmental data) may be a type of shared data 345.

Sensor data 350 may also exist in volatile memory 320 and/or memorystorage 315 as a type of data recorded and collected from an onboardsensor or from another node. For example, sensor data 350 may includetemperature readings from a temperature sensor onboard an ID node and/orhumidity readings from a humidity sensor in another ID node (e.g., fromanother of the ID nodes within container 210 as shown in FIG. 2).

Thus, an ID node (such as node 120 a shown in FIG. 3) is a lower costwireless node that communicates with other ID nodes and master nodes viaa short-range radio with variable RF characteristics, can be associatedwith other nodes, can broadcast to and scan for other nodes, associatedwith other nodes, and store/exchange information with other nodes.

Master Node

A master node, such as master node 110 a shown in more detail in FIG. 4,shares many ID node features but generally expands upon them in order tofunction as a bridge to the server 100. In general, while an ID node isa type of lower level node in an exemplary wireless node network, amaster node is a type of higher level node. An exemplary master node maybe in a fixed location or otherwise stationary, while other examplemaster nodes may be implemented as movable and mobile devices.

Referring now to FIG. 4, exemplary master node 110 a comprises aprocessing or logic unit 400 coupled to a short-range communicationinterface 480, memory storage 415, volatile memory 420, clock/timer 460,and battery/power interface 470. In some embodiments, the short-rangecommunication interface 480 may have variable power characteristics,such as receiver sensitivity and RF output power level. Those skilled inthe art will appreciate that processing unit 400 is logic, such as amicroprocessor or microcontroller, which generally performs computationson data and executes operational and application program code and otherprogram modules within the master node 110 a.

In general, those skilled in the art will appreciate that thedescription of hardware with respect to ID node 110 a in FIG. 4 appliesto the similar hardware and software features appearing in each type ofnode, including a master node. Those skilled in the art will appreciatethat exemplary master node 110 a is a hardware-based component that mayimplement processor 400 with a single processor or logic unit, a morepowerful multi-core processor, or multiple processors depending upon thedesired implementation. In one embodiment, processing unit 400 may beimplemented with a low power microprocessor and associated peripheralcircuitry. Less complex microcontrollers or discrete circuitry may beused to implement processing unit 400 as well as more complex andsophisticated general purpose or dedicated purpose processors.

In yet another embodiment, exemplary processing unit 400 may beimplemented by a low power ARM1176JZ-F application processor used aspart of a single-board computer, such as the Raspberry Pi Computer ModelB-Rev-2. The ARM application processor is embedded within a Broadcom®BCM2835 system-on-chip (SoC) deployed in the Raspberry Pi Computer. Inthis embodiment, the Raspberry Pi Computer device operates as a core ofexemplary master node 110 a and includes a Secure Digital memory cardslot and flash memory card operating as memory storage 415, a 512 MbyteRAM memory storage operating as volatile memory 420, an operating system(such as Linux) stored on memory storage 415 and running in volatilememory 420, and peripherals that implement clock/timer 460, and a powersupply operating as a power interface 470.

Like short-range interface 375 in ID node 120 a, exemplary master node110 a includes a short-range communication interface 480 as aprogrammable radio and an omni-directional antenna coupled to theprocessing unit 400. In some embodiments, the short-range communicationinterface 480 may have variable RF power characteristics, such asreceiver sensitivity and/or RF output signal power level. In someembodiments, interface 480 may use an antenna with a different antennaprofile when directionality may be desired. Examples of short-rangecommunication interface 480 may include other hardware (not shown) foroperatively coupling the device to a specific short-range communicationpath (e.g., a Bluetooth® Low Energy (BLE) connection path communicatingat 2.4 GHz). While BLE is used in one embodiment to enable a short-rangecommunication protocol, variable power short-range interface 480 may beimplemented with other low power, short-range communication protocols,such as ultra-low power communication protocols used with ultra-widebandimpulse radio communications, ZigBee protocols, IEEE 802.15.4 standardcommunication protocols, and the like.

In one embodiment, various RF characteristics of the radio'stransceiver, such as the RF output power and the RF receiver sensitivitymay be dynamically and programmatically varied under control ofprocessing unit 400. In other embodiments, further RF characteristics ofthe radio's transceiver may be programmatically varied, such asfrequency, duty cycle, timing, modulation schemes, spread spectrumfrequency hopping aspects, etc., as needed to flexibly adjust the RFoutput signal as needed depending upon a desired implementation andanticipated use of exemplary master node 110 a. In other words,embodiments of master node 110 a (or any other master node) may haveprogrammatically adjustable RF characteristics (such as an adjustable RFoutput signal power, an adjustable RF receiver sensitivity, the abilityto switch to a different frequency or frequency band, etc.).

In addition to the short-range communication interface 480, exemplarymaster node 110 a includes a medium and/or long-range communicationinterface 485 to provide a communication path to server 100 via network105. Those skilled in the art will appreciate that in some embodiments,an exemplary communication interface deployed may be considered toembody a short-range communication interface (such as interface 480) ora medium/long range communication interface (such as interface 485).However, in more general embodiments, reference to a communicationinterface may include an interface that collectively implements aplurality of different exemplary data communication interfaces whilestill being generally referenced as “a communication interface” or“wireless communication interface.”

In one embodiment, communication interface 485 may be implemented with amedium range radio in the form of an IEEE 802.11g compliant Wi-Fitransceiver. In another embodiment, communication interface 485 may beimplemented with a longer range radio in the form of a cellular radio.In yet another embodiment, both a Wi-Fi transceiver and a cellular radiomay be used when best available or according to a priority (e.g., firstattempt to use the Wi-Fi transceiver if available due to possible lowercosts; and if not, then rely on the cellular radio). In other words, anembodiment may rely upon the longer range cellular radio part ofinterface 485 as an alternative to the medium range Wi-Fi transceiverradio, or when the medium range radio is out of reach from a connectinginfrastructure radio within network 105. Thus, in these embodiments,medium and/or long-range communication interface 485 may be used tocommunicate captured node information (e.g., profile data 430,association data 440, shared data 445, sensor data 450, and locationdata 455) to server 100.

The battery/power interface 470 for master node 110 a generally powersthe circuitry implementing master node 110 a. In one embodiment,battery/power interface 470 may be a rechargeable power source. Forexample, a master node may have a rechargeable power source along with asolar panel that charges the power source in order to help facilitatedeployment of the master in a remote location. In another embodiment,battery/power interface 470 may be a non-rechargeable power sourceintended to be disposed of after use. In yet another embodiment,battery/power interface 470 may be a power interface connector (such asa power cord and internal power supply on master node 110 a). Thus, whenan exemplary master node is in a fixed or stationary configuration, itmay be powered by a power cord connected to an electrical outlet, whichis coupled to an external power source. However, other mobile masternodes may use an internal power source, such as a battery.

The clock/timer 460 for master node 110 a generally provides one or moretiming or counting circuits used in, for example, counter, time delay,pulse generation, and oscillator applications. In an embodiment wheremaster node 110 a conserves power by entering a sleep or dormant statefor a predetermined time period as part of overall power conservationtechniques, clock/timer 460 assists processing unit 400 in managingtiming or counting operations.

Optionally, an embodiment may also implement master node 110 a asincluding one or more sensors 465 (similar to sensors deployed on IDnode based Sensor nodes and described above with respect to FIG. 3).Additionally, an embodiment of master node 110 a may also provide a userinterface 405 to indicate status and allow basic interaction for reviewof captured node data and interaction with nodes and server 100. In oneembodiment, user interface 405 may provide a display, interactivebuttons or soft keys, and a pointing device to facilitate interactionwith the display. In a further embodiment, a data entry device may alsobe used as part of the user interface 405. In other embodiments, userinterface 405 may take the form of one or more lights (e.g., statuslights), audible input and output devices (e.g., a microphone andspeaker), or touchscreen.

As previously noted, an exemplary master node, such as master node 110a, may be positioned in a known fixed location or, alternatively,includes dedicated location positioning circuitry 475 (e.g., GPScircuitry) to allow the master node self-determine its location or todetermine its location by itself. In other embodiments, alternativecircuitry and techniques may be relied upon for location circuitry 475(rather than GPS), such as location circuitry compatible with othersatellite-based systems (e.g., the European Galileo system, the RussianGLONASS system, the Chinese Compass system), terrestrial radio-basedpositioning systems (e.g., cell phone tower-based or Wi-Fi-basedsystems), infrared positioning systems, visible light based positioningsystems, and ultrasound-based positioning systems).

Regarding memory storage 415 and volatile memory 420, both areoperatively coupled to processing unit 400 in exemplary master node 110a. Both memory components provide program elements used by processingunit 400 and maintain and store data elements accessible to processingunit 400 (similar to the possible data elements stored in memory storage315 and volatile memory 320 for exemplary ID node 120 a).

In the embodiment shown in FIG. 4, memory storage 415 maintains avariety of executable program code (e.g., master control and managementcode 425), data similar to that kept in an ID node's memory storage 315(e.g., profile data 430, security data 435, association data 440, shareddata 445, sensor data 450, and the like) as well as other data morespecific to the operation of master node 110 a (e.g., location data 455that is related to the location of a particular node). Like memorystorage 315, memory storage 415 is a tangible, non-transient computerreadable medium on which information (e.g., executable code/modules,node data, sensor measurements, etc.) may be kept in a non-volatile andnon-transitory manner.

Like volatile memory 320 in ID node 120 a, volatile memory 420 istypically a random access memory (RAM) structure used by processing unit400 during operation of the master node 110 a. Upon power up of masternode 110 a, volatile memory 120 may be populated with an operationalprogram (such as master control and management code 425) or specificprogram modules that help facilitate particular operations of masternode 110 a. And during operation of master 110 a, volatile memory 420may also include certain data (e.g., profile data 430, security data435, association data 440, shared data 445, sensor data 450, and thelike) generated as the master node 110 a executes instructions asprogrammed or loaded from memory storage 415.

Master Control & Management Code

Generally, an embodiment of master control and management code 425 is acollection of software features implemented as programmatic functions orprogram modules that generally control the behavior of a master node,such as master node 110 a. In one embodiment, master control andmanagement code 425 generally comprises several programmatic functionsor program modules including (1) a node advertise and query (scan) logicmanager, which manages how and when a node communicates; (2) aninformation control and exchange manager, which manages whether and howinformation may be exchanged between nodes; (3) a node power manager,which manages power consumption and aspects of RF output signal powerand/or receiver sensitivity for variable short-range communications; (4)an association manager focusing on how the node associates with othernodes; and (5) a location aware/capture module to determine nodelocation.

Master Node Program Modules and ID Node Modules

In an exemplary embodiment, program modules (1)-(4) of master nodecontrol and management code 425 generally align with the functionalityof similarly named program modules (1)-(4) of node control andmanagement code 325 as described above with respect to FIG. 3.Additionally, as node control and management code 325 may also comprisean airborne mode program module, those skilled in the art willappreciate and understand that master node control and management code425 may also comprise a similar functionality airborne mode programmodule in order to allow advantageous operations of a master node whileairborne. However, and consistent with examples set forth below, suchmodules may have some differences when in a master node compared withthose controlling an ID node.

Location Aware/Capture Module

In addition to exemplary program modules (1)-(4) of code 425, anexemplary embodiment of master node control and management code 425 willfurther comprise an exemplary location aware/capture module related tonode location (more generally referred to as a location manager modulefor a master node). In general, the exemplary location aware/capturemodule deployed in an exemplary master node may determine its ownlocation and, in some embodiments, the location of a connected node.Embodiments of the exemplary location aware/capture module may work inconjunction with location manager program code residing and operating ina server (e.g., as part of server control and management code 525) whendetermining node locations of other nodes, as discussed in more detailherein.

In one embodiment, a master node may be positioned in a known, fixedlocation. In such an embodiment, the exemplary location aware/capturemodule may be aware that the master node location is a known, fixedlocation, which may be defined in a fixed, preset, or preprogrammed partof memory storage 415 (e.g., information in the location data 455maintained in memory storage 415). Examples of such location informationmay include conventional location coordinates or other descriptivespecifics that identify the location of the master node. In anotherembodiment where the master node may not be inherently known or a fixedlocation at all times (e.g., for a mobile master node), the exemplarylocation aware/capture module may communicate with location circuitry,such as GPS circuitry 475 on a master node, to determine the currentlocation of the master node.

In an embodiment, the location of the master node may be communicated tothe server, which may use this location information as part of managingand tracking nodes in the wireless node network. For example, if anexemplary master node is mobile and has determined a new currentlocation using location circuitry 475, the master node may provide thatnew current location for the master node to the server. Additionally,when the master node's exemplary location aware/capture moduledetermines the location of a node associated with the master node, themaster node may also provide the location of that node associated withthe master node to the server.

Server

While FIGS. 3 and 4 illustrate details of hardware and software aspectsof an exemplary ID node and exemplary master node, respectively, FIG. 5provides a more detailed diagram of an exemplary server that may operateas part of an exemplary wireless node network in accordance with anembodiment of the invention. In an exemplary embodiment, server 100 maybe referred to as an Association and Data Management Server (ADMS) thatmanages the nodes, collects information from the nodes, stores thecollected information from the nodes, maintains or has access to contextdata related to the environment in which the nodes are operating, andmay provide information about the nodes (e.g., status, sensorinformation, etc.) to requesting entities. Further details on variousembodiments that take advantage of this functionality are explainedbelow. Those skilled in the art will appreciate that node density,geographic installation characterization, and network connectively areall types of examples of factors that may impact a final architecturedesired for an embodiment of a wireless node network.

Referring now to FIG. 5, exemplary server 100 is shown as a networkedcomputing platform capable of connecting to and interacting with atleast the wireless master nodes. In other embodiments, exemplary server100 is also capable of connecting to and interacting with one or moreuser access devices. Those skilled in the art will appreciate thatexemplary server 100 is a hardware-based component that may beimplemented in a wide variety of ways. For example, server 100 may use asingle processor or may be implemented as one or more part of amulti-processor component that communicates with devices (such as useraccess devices 200, 205) and wireless nodes (such as master node 110 a).

In general, those skilled in the art will further appreciate that server100 may be implemented as a single computing system, a distributedserver (e.g., separate servers for separate server related tasks), ahierarchical server (e.g., a server implemented with multiple levelswhere information may be maintained at different levels and tasksperformed at different levels depending on implementation), or a serverfarm that logically allows multiple distinct components to function asone server computing platform device from the perspective of a clientdevice (e.g., devices 200, 205 or master node 110 a). In some regionaldeployments, an exemplary server may include servers dedicated forspecific geographic regions as information collected within differentregions may include and be subject to different regulatory controls andrequirements implemented on respective regional servers.

Likewise, while the embodiment shown in FIG. 5 illustrates a singlememory storage 515, exemplary server 100 may deploy more than one memorystorage media. And memory storage media may be in differingnon-transitory forms (e.g., conventional hard disk drives, solid statememory such as flash memory, optical drives, RAID systems, cloud storageconfigured memory, network storage appliances, etc.).

At its core, exemplary server 100 shown in FIG. 5 comprises a processingor logic unit 500 coupled to a network interface 590, which facilitatesand enables operative connections and communications through network 105with one or more master nodes as well as, in some embodiments, useraccess devices, such as devices 200, 205. In one embodiment, server 100may include a medium and/or long-range communication interface 595 withwhich to more directly communicate with one or more master nodes. Usingthese communication paths as well as program code or program modules(such as server control and management code 525), the server 100generally operates to coordinate and manage information related to an IDnode as an item associated with the ID node physically moves from onelocation to another.

As a computing platform, the processing unit 500 of exemplary server 100is operatively coupled to memory storage 515 and volatile memory 520,which collectively store and provide a variety of executable programcode (e.g., server control and management code 525), data similar tothat kept in a master or ID node's respective memory storage (e.g.,profile data 530, security data 535, association data 540, shared data545, sensor data 550, location data 555) and context data 560 related tothe environment in which the nodes are operating (e.g., informationgenerated from within the wireless node network and information createdexternal to the wireless node network).

Like memory storage 315 and storage 415, memory storage 515 is atangible, non-transient computer readable medium on which information(e.g., executable code/modules (e.g., server control and management code525), node-related data (e.g., profile data 530, security data 535,association data 540, location data 555, etc.), measurement information(e.g., a type of shared data 545, sensor data 550, etc.), andinformation on the contextual environment for the nodes (e.g., contextdata 560) may be kept in a non-volatile and non-transitory manner.

Those skilled in the art will appreciate that the above identificationof particular program code and data are not exhaustive and thatembodiments may include further executable program code or modules aswell as other data relevant to operations of a processing-based device,such as an ID node, a master node, and a server.

Context Data

As noted above, server 100 may access context data 560 as part ofmanaging nodes in the wireless node network. The exemplary server 100may contain a collection of such context data 560 in a context database565 according to an embodiment. As illustrated in FIG. 5, exemplarycontext database 565 is a single database accessible by processing unit500 internal to server 100. Those skilled in the art will readilyunderstand that other configurations that provide an accessiblecollection of context data 560 are possible and contemplated within thescope and principles of embodiments of the invention. For example,context database 565 may be an externally accessible database (ormultiple databases), such as an accessible storage maintained outsidethe server 100 via a dedicated interface or a network storage device (ornetwork attached storage (NAS) unit). In yet another embodiment, thecontext database may be separately maintained by an external databaseserver (not shown) that is distinct from server 100, but accessiblethrough a communication path from server 100 to a separate databaseserver (e.g., via network 105). Furthermore, those skilled in the artwill appreciate that context database 565 may be implemented with cloudtechnology that essentially provides a distributed networked storage ofcollections of information (such as context data 560, sensor data 550,shared data 545, etc.) accessible to server 100.

Within context database 565, an exemplary embodiment of the collectionof context data 560 may be maintained that generally relates to anenvironment in which the nodes are operating or anticipated to beoperating. In more detail, the context data 560 may generally relate towhat a similar node has experienced in a similar environment to what agiven node is presently experiencing or is anticipated to experience asthe given node moves.

In a general example, an environment in which a node may be actually oranticipated to be operating may include different types ofenvironments—for example, an electronic communication environment (e.g.,an RF environment that may be cluttered with signals or includematerials or structure that may impede or otherwise shield RFcommunications), a physical environment of an anticipated path alongwith the identified node moves (e.g., temperature, humidity, security,and other physical characteristics), a conveyance environment related tohow a node may move or be anticipated to be moving (e.g., speed andother parameters of a truck, airplane, conveyor system), and a densityenvironment related to the density of nodes within an area near aparticular node (e.g., how many nodes are anticipated to occupy acorridor, such as structure 2200 shown in FIG. 22A, or a storagefacility through which a particular ID node is anticipated to transit onits shipping path).

In light of these different aspects of a node's operating environment,exemplary context data 560 may provide information related to differentstructures and conditions related to movement of an item (e.g., aparticular type of courier device, vehicle, facility, transportationcontainer, etc.). Such information may be generated by an entityoperating the wireless node network, such as a shipping company.Additionally, exemplary context data 560 may include third party datagenerated external to the wireless node network. Thus, context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention.

In general, FIG. 5 illustrates exemplary types of context data 560 beingmaintained in database 565 and in volatile memory 520. Those skilled inthe art will appreciate that context data 560 may also be maintained inother data structures, in addition to or instead of maintaining suchinformation in a database. As illustrated in FIG. 5, exemplary types ofcontext data 560 may include but are not limited to scan data 570,historic data 575, shipment data 580, layout data 585, RF data 587, and3^(rd) party data.

Scan data 570 is generally data collected for a particular item relatedto an event. For example, when an item is placed in a package (such aspackage 130), a label may be generated and placed on the exterior of thepackage. The label may include a visual identifier that, when scanned byan appropriate scanning device capable of capturing, identifies thepackage. The information generated in response to scanning theidentifier (a type of event), may be considered a type of scan data.Other scan data 570 may include, for example, general inventory datagenerated upon manual entry of information related to the package;captured package custodial control data; and bar code scan data.

Historic data 575 is generally data previously collected and/or analyzedrelated to a common characteristic. Historic data 575 embodiesoperational knowledge and know-how for a particular characteristicrelevant to operations of the wireless node network. For example, thecommon characteristic may be a particular event (e.g., movement of anitem from an open air environment to within a particular closedenvironment, such as a building), a type of item (e.g., a type ofpackage, a type of content being shipped, a location, a shipment path,etc.), a success rate with a particular item (e.g., successfulshipment), and the like. Another example of historic data 575 mayinclude processing information associated with how an item has beenhistorically processed as it is moved from one location to another(e.g., when moving within a particular facility, processing informationmay indicate the item is on a particular conveyor and may includeinformation about the conveyor (such as speed and how long it isanticipated the item will be on the conveyor)).

Shipment data 580 is generally data related to an item being moved fromone location to another location. In one embodiment, shipment data 580may comprise a tracking number, content information for an item beingshipped, address information related to an origin and destinationlocations, and other characteristics of the item being moved.

Layout data 585 is generally data related to the physical area of one ormore parts of an anticipated path. For example, an embodiment of layoutdata 585 may include building schematics and physical dimensions ofportions of a building in which a node may be transiting. An embodimentmay further include density information associated with physical areasto be transited and anticipated numbers of potential nodes in thoseareas as types of layout data. In another example, an embodiment oflayout data may include a configuration of how a group of packages maybe assembled on a pallet, placed into a shipping container (e.g., a unitload device (ULD)) that helps move a collection of items on variousforms with single mode or intermodal transport.

RF data 587 is generally signal degradation information about a signalpath environment for a particular type of node and may relate toparticular adverse RF conditions that may cause signal fluctuations,interference, or other degradation from the otherwise optimal signalpath environment for that type of node. For example, RF data may includeshielding effects when using a particular packaging or location,shielding effects when the package is within a particular type ofcontainer or assembled as part of a palletized shipment, shieldingeffects when particular content is shipped, and other physical andelectronic interference factors.

Third party data 589 is an additional type of context data 560 thatgenerally includes data generated outside the network. For example,third party data may include weather information associated withparticular areas to be transited as the item is moved along ananticipated path from one location to another. Those skilled in the artwill appreciate other types of third party data that relate to physicaland environmental conditions to be faced by an item being moved from onelocation to another may also be considered context data 560.

The use of context data, such as context data 560 described above,advantageously helps server 100 better manage movement of items, providebetter location determination, enhance intelligent operation andmanagement of different levels of the wireless node network, and provideenhanced visibility to the current location and status of the itemduring operation of the wireless node network. In one embodiment, servercontrol and management code 525 may provide such functionality thatenables the wireless node network to be contextually aware andresponsive.

Server Control & Management Code

Generally, server control and management code 525 controls operations ofexemplary server 100. In an embodiment, server control and managementcode 525 is a collection of software features implemented asprogrammatic functions in code or separate program modules thatgenerally control the behavior of server 100. Thus, exemplary servercontrol and management code 525 may be implemented with severalprogrammatic functions or program modules including, but not limited to,(1) a server-side association manager, which provides a framework formore robust and intelligent management of nodes in the wireless nodenetwork; (2) a context-based node manager, which enhances management ofnodes in the wireless node network based upon context data; (3) asecurity manager, which manages secure pairing aspects of nodemanagement; (4) a node update manager, which provides updated ordifferent programming for a particular node and shares information withnodes; (5) a location manager for determining and tracking the locationof nodes in the network; and (6) an information update manager, whichservices requests for information related to the current status of anode or generally providing information about a node or collected from anode.

Server-Side Association Manager

The server-side association manager (also referred to as a server-sideassociation management function) is generally a program module inexemplary code 525 that is responsible for intelligently managing thenodes in the wireless node network using a secure information framework.In an embodiment, this framework may be implemented to be acontext-driven, learning sensor platform. The framework may also enablea way for information (such as RF scan, location, date/time, and sensordata) to be securely shared across nodes, a way to change the behaviorof a node, and for a node to know it is considered “missing.” Theframework established during operation of the server-side associationmanager allows the network of nodes to be managed as a system withenhanced and optimized accuracy of determining the physical location ofeach ID Node. Further information regarding particular embodiments ofsuch an association management framework and methods are explained belowin more detail.

Context-Based Association Manager

The context-based node manager is generally a program module inexemplary code 525 that is responsible for incorporating context data aspart of management operations to provide an enhanced data foundationupon which visibility of the nodes may be provided. In some embodiments,the context-based node manager may be implemented as part of theserver-side association manager while other embodiments may implementthe context-based node manager as a separate program module.

In one embodiment, the enhanced data foundation relies upon contextdata, such as context data 560 (e.g., scan data 570, historic data 575,shipment data 580, layout data 585, and other third party contextualdata providing information regarding the conditions and environmentsurrounding an item and ID node moving from one location to another.Such context data (e.g., the network know-how, building layouts, andoperational knowledge of nodes and shipping paths used with the wirelessnode network) may provide the enhanced building blocks that allow theserver 100 to manage tracking and locating of nodes in a robustlyenriched contextual environment. In an embodiment, context-basedmanagement provides visibility to the system through data analysis forwhen and how associations should be expected as the nodes travel throughthe wireless node network. In other embodiments, it may provide thefoundation for better understanding RF signal degradation, which can becaused by the operating environment, packaging, package content, and/orother packages related to an item and its ID node.

Security Manager

The security manager module, which may be implemented separately or aspart of the association manager module in exemplary server control andmanagement code 525, helps with associating two nodes in the wirelessnode network by managing aspects of secure pairing of the nodes. In oneembodiment, security manager module provides the appropriate pairingcredentials to allow a node to securely connect to another node. Thus,when a node desires to connect to another node, an embodiment requiresappropriate pairing credentials be generated by the server, provided tothe nodes, and observed within the nodes to allow for a successfulconnection or association of nodes.

In operation, a node (such as master node 110 a) identifies the addressof the node (such as ID node 120 a) to whom it desires to connect. Withthis address, the node prepares a pairing request and sends the requestto the server 110. The server 100 operates under the control of thesecurity manager module of the association manager, and determineswhether the requesting node should be connected or otherwise associatedwith the other node. If not, the server does not issue the requestedsecurity credentials. If so and in accordance with the desiredassociation management paradigm set by the association manager of code525, server provides the requested credentials necessary for asuccessful wireless pairing and the establishment of securecommunications between the associated nodes.

Node Update Manager

The exemplary server control and management code 525 may include a nodeupdate manager module that provides updated programming information tonodes within the wireless node network and collects information fromsuch nodes (e.g., shared data 545, sensor data 550). The node updatemodule may be implemented separately or as part of the associationmanager module in exemplary server control and management code 525.

Providing an update to a node's programming may facilitate and enabledistribution of node functions to save power and better manage the nodesas a system. For example, one embodiment may alter the functionalresponsibility of different nodes depending on the context orassociation situation by temporarily offloading responsibility for aparticular function from one node to another node. Typically, the serverdirects other nodes to change functional responsibility. However, insome embodiments, a master node may direct other nodes to alterfunctional responsibility.

Sharing information between nodes and with server (e.g., via anexemplary node update manager) facilitates collecting information from anode and sharing information with other nodes as part of an associationmanagement function of server 100. For example, one embodiment maycollect and share RF scan data (a type of shared data 545), informationabout a node's location (a type of location data 555), systeminformation about date/time (another type of shared data 545), andsensor measurements collected from sensor nodes (a type of sensor data550).

Location Manager

The exemplary server control and management code 525 may include alocation manager module that helps determine and track node locations.In a general embodiment, the location of a node may be determined by thenode itself (e.g., a master node's ability to determine its own locationvia location circuitry 475), by a node associated with that node (e.g.,where a master node may determine the location of an ID node), by theserver itself (e.g., using location information determined by one ormore techniques implemented as part of code 525), and by a combinedeffort of a master node and the server.

In general, an exemplary ID node may be directly or indirectly dependenton a master node to determine its actual physical location. Embodimentsmay use one or more methodologies to determine node location. Forexample and as more specifically described below, possible methods fordetermining node location may relate to controlling an RF characteristicof a node (e.g., an RF output signal level and/or RF receiversensitivity level), determining relative proximity, consideringassociation information, considering location adjustments for contextinformation and an RF environment, chaining triangulation, as well ashierarchical and adaptive methods that combine various locationmethodologies. Further information and examples of how an exemplarylocation manager module may determine a node's location in accordancewith such exemplary techniques are provided in more detail below.

Additionally, those skilled in the art will appreciate that it may alsobe possible to determine what constitutes an actionable location versusactual location based upon contextual information about the item beingtracked. For example, a larger item may require relatively less locationaccuracy than a small item such that operational decisions and statusupdates may be easier implemented with knowledge of context. If the sizeof the item is known, the location accuracy can be tuned accordingly.Thus, if a larger item is to be tracked, or if the system's contextualawareness of it is such that lower location accuracy can be used, astronger signal and thus wider area of scanning may be employed, whichmay help in situations where RF interference or shielding is an issue.

Information Update Manager

The exemplary server control and management code 525 may include aninformation update manager module that provides information related tooperations of the wireless node network and status of nodes. Suchinformation may be provided in response to a request from a deviceoutside the wireless node network (such as user access device 200). Forexample, someone shipping an item may inquire about the current statusof the item via their laptop or smartphone (types of user accessdevices), which would connect to server 100 and request suchinformation. In response, the information update manager module mayservice such a request by determining which node is associated with theitem, gathering status information related to the item (e.g., locationdata, etc.), and provide the requested information in a form that istargeted, timely, and useful to the inquiring entity.

In another example, a user access device may connect to server 100 andrequest particular sensor data from a particular node. In response,information update manager may coordinate with node update manager, andprovide the gathered sensor data 545 as requested to the user accessdevice.

Node Filtering Manager

An embodiment of exemplary server control and management code 525 mayoptionally comprise a node filtering manager, which helps manage thetraffic of nodes with a multi-level filtering mechanism. The filteringessentially sets up rules that limit potential associations andcommunications. An example of such a node filtering management maydefine different levels or modes of filtering for a master node (e.g.,which ID nodes can be managed by a master node as a way of limiting thecommunication and management burdens on a master node).

In one example, a “local” mode may be defined where the ID node onlycommunicates and is managed by the assigned master node at the locationwhere the last wireless node contact back to server 100 and/or wherethird party data indicates the assigned master node and ID node are inphysical and wireless proximity. Thus, for the “local” mode of trafficfiltering, only the assigned master node communicates and processesinformation from a proximately close and assigned ID node.

Moving up to a less restrictive filtering mode, a “regional” mode offiltering may be defined where the ID node may communicate and bemanaged by any master node at the location last reported back to server100 and/or where third party data indicates the ID node is located.Thus, for the “regional” mode of traffic filtering, any master node nearthe ID node may communicate and process information from that ID node.This may be useful, for example, when desiring to implement a limit onassociations and pairings to within a particular facility.

At the least restrictive filtering mode, a “global” mode of filteringmay be defined as essentially system-wide communication where the IDnode may be allowed to communicate and be managed by any master node. Inother words, the “global” mode of traffic filtering allows any ID nodewithin the wireless node network to communicate information through aparticular master node near the ID node may communicate and processinformation from that ID node.

Thus, with such exemplary filtering modes, an ID node in a certaincondition (e.g., distress, adverse environmental conditions, adverseconditions of the node, etc.) may signal the need to bypass anyfiltering mechanism in place that helps manage communications andassociation by using the “Alert” Status Flag. In such an example, thiswould operate to override any filtering rules set at the Master Nodelevel in order to allow an ID node to be “found” and connect to anothernode.

Thus, exemplary server 100 is operative, when executing code 525 andhaving access to the types of data described above, to manage the nodes,collect information from the nodes, store the collected information fromthe nodes, maintain or have access to context data related to theenvironment in which the nodes are operating, and provide informationabout the nodes (e.g., status, sensor information, etc.) to a requestingentity.

Node Communication & Association Examples

To better illustrate how exemplary management and communicationprinciples may be implemented within an exemplary wireless node network,FIGS. 8-12 provide several examples of how exemplary components of thewireless node network may generally communicate (advertising &scanning), associate, and exchange information during different types ofoperations in various embodiments. FIGS. 22A-C also provide a moredetailed application of such exemplary association and communicationactivities when an exemplary ID node moves along a transit path (e.g.,through a corridor) and is tracked and managed by different master nodesand a server in an embodiment.

Node Advertising Cycle Example

As generally explained above, a node may have several different types ofadvertising states in which the node may be connectable with other nodesand may communicate with other nodes. And as a node moves within awireless node network, the node's state of advertising and connectionmay change as the node disassociates with a previously connected node,associates with a new node, or finds itself not associated with othernodes. In some situations, a node may be fine and in normal operationnot be connected or associated with another node. However, in othersituations, a node may raise an issue with potentially being lost if ithas not connected with any other node in a very long period of time. Assuch, a node may go through different types of advertising states inthese different operational situations.

Generally, a node may be in a state where it is not connectable withother nodes for a certain period of time (also referred to as anon-connectable interval). But later, in another state, the node maywant to be connected and advertises as such for a defined connectableperiod (also referred to as a connectable interval). As the nodeadvertises to be connected, the node may expect to be connected at somepoint. In other words, there may be a selectable time period withinwhich a node expects to be connected to another node. However, if thenode is not connected to another node within that period of time(referred to as an Alert Interval), the node may need to take specificor urgent action depending upon the circumstances. For example, if anode has not been connected to another node for 30 minutes (e.g., anexample alert interval), the node may change operation internally tolook “harder” for other nodes with which to connect. More specifically,the node may change its status flag from an Alert Level 0 (no issue,operating normal) to Alert Level 2 in order to request that anyavailable master node acknowledge receipt of the advertisement packetbroadcasted by the node seeking a connection.

FIG. 8 is a diagram illustrating exemplary advertising states (orinformation exchange and node connectability states) and factorsinvolved in transitions between the states by an exemplary ID node in awireless node network in accordance with an embodiment of the invention.Referring now to FIG. 8, three exemplary states for a node areillustrated as part of an exemplary advertising cycle for thenode—namely, an ID Node Non-Connectable Advertising state 805, an IDNode Discoverable Advertising state 815, and an ID Node GeneralAdvertising state 830. Transitions between these states will depend onfactors related to expirations of the types of intervals describedabove. In an embodiment, the duration of each of these intervals willdepend upon the system implementation and the contextual environmentwithin which the ID node is operating. Such time intervals may, forexample, be set by server 100 as part of data (e.g., profile data,association data, context data) provided to the node when updating thenode and managing operations of the node.

Referring to the example illustrated in FIG. 8, an exemplary ID node mayhave an alert interval set at, for example, 30 minutes, and be in IDNode Non-Connectable Advertising state 805 with a non-connectableinterval set at 5 minutes. In state 805, the ID node may broadcast oradvertise, but is not connectable and will not receive a SCAN_REQmessage (a type of request for more information sent to the advertisingnode from another node). Thus, the ID node in state 805 in this examplemay advertise in a non-connectable manner for at least 5 minutes butexpects to be connected within 30 minutes.

If the alert interval has not yet elapsed (factor 810) and thenon-connectable interval is still running (factor 825), the ID nodesimply stays in state 805. However, if the alert interval has notelapsed (factor 810) and the non-connectable interval elapses (factor825), the ID node will enter a mode where it wants to try to connect toanother node for a period of time (e.g., a 1 minute connectableinterval) and will move to the ID Node General Advertising state 830 inthe exemplary advertising cycle of FIG. 8. In state 830, as long as theconnectable interval is running, the ID node will stay in this statewhere it is connectable to another node and will receive SCAN_REQ typesof requests from other nodes in response to the advertising packets theID node is broadcasting. However, when the connectable interval (e.g.,the 1 min period) elapses or expires (factor 835), the ID node returnsback to the Non-connectable Advertising state 805 for either the nexttime the non-connectable interval elapses (and the ID node again triesto connect in state 830) or the alert interval finally elapses (and theID node finds itself in a situation where it has not connected toanother node despite its efforts to connect in state 830).

When the alert interval finally elapses (factor 810), the ID node movesto the ID Node Discoverable Advertising state 815. Here, the ID node isnot yet connectable but will receive a SCAN_REQ type of request fromother nodes in response to advertising packets the ID node isbroadcasting. In this state 815, the exemplary ID node may alter itsstatus flag to indicate and reflect that its alert interval has expiredand that the node is now no longer in normal operation. In other words,the ID node may change the status flag to a type of alert status beingbroadcasted to indicate the ID node urgently needs to connect withanother node. For example, the status flag of the advertising packetbroadcast by the ID node may be changed to one of the higher AlertLevels depending on whether the node needs to upload data (e.g., AlertLevel 3 status) or synchronize timer or other data with another node(e.g., Synchronize status). With this change in status flag, and the IDnode in state 815 broadcasting, the ID node awaits to receive a requestfrom another node that has received the broadcast and requested moreinformation via a SCAN_REQ message (factor 820) sent to the ID node fromthat other node. Once a SCAN_REQ message has been received by the IDnode (factor 820), the ID node that went into the alert mode because ithad not connected with another node within the alert interval canconnect with that other node, upload or share data as needed, and thenshift back to state 805 and restart the alert interval andnon-connectable intervals.

Master Node to ID Node Association Example

Advertising (broadcasting) and scanning (listening) are ways nodes maycommunicate during association operations. FIGS. 9-12 provide examplesof how network elements of a wireless node network (e.g., ID nodes,master nodes, and a server) may communicate and operate when connectingand associating as part of several exemplary wireless node networkoperations.

FIG. 9 is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary master-to-ID node association in accordancewith an embodiment. Referring now to FIG. 9, exemplary master node M1910 a is illustrated within communication range of exemplary ID node A920 a. Master node M1 910 a also has a communication path back to server900. As shown, master node M1 910 a is in a scanning or listening mode(e.g., indicated by the “M1 _(scan)” label) while ID node A 920 a is inan advertising or broadcasting mode (e.g., indicated by the “A_(adv)”label). In this example, M1 master node 910 a has captured the addressof ID node A 920 a through A's advertising of at least one advertisingdata packet, and has reported it to the server 900. In this manner, thecapturing and reporting operations effectively create a “passive”association between the nodes and proximity-based custodial control.Such an association may be recorded in the server, such as server 900,as part of association data, such as association data 540.

In another embodiment, passive association between a master node and IDnode may be extended to an “active” association or connection. Forexample, with reference to the embodiment shown in FIG. 9, server 900may instruct master node M1 910 a to associate, connect, or otherwisepair with ID node A 920 a, and forwards the required securityinformation (e.g., PIN credentials, security certificates, keys) tomaster node M1 910 a. Depending on the advertising state of ID node A920 a, ID node A 910 a may only be visible (discoverable) but notconnectable. In such a situation, the master node M1 910 a must waituntil ID node A 920 a is in a connectable state (e.g., the ID NodeGeneral Advertising state) and can be paired. As discussed above withreference to FIG. 8, each ID node has a certain time window during eachtime period where it can be paired or connected.

In this example, when the ID node A 920 a is successfully paired withmaster node M1 910 a, ID node A 920 a may no longer advertise itsaddress. By default, only an unassociated device will advertise itsaddress. A paired or associated node will only advertise its address ifinstructed to do so.

ID Node to ID Node Association Example

In various embodiments, an ID node may associate with or connect toother ID nodes. FIG. 10 is a diagram illustrating exemplary componentsof a wireless node network during an exemplary ID-to-ID node associationin accordance with an embodiment of the invention. Referring now to FIG.10, exemplary master node M1 910 a, ID node A 920 a, and server 900 aresimilarly disposed as shown in FIG. 9, but with the addition of ID nodeB 920 b, which is within communication range of ID node A 920 a. In thisexample, ID node A 920 a is running in query (scan) mode (e.g.,A_(scan)) listening for ID node B 920 b. When ID node A 910 a detects IDnode B 920 b advertising (e.g., B_(adv)) with one or more advertisingdata packets as part of an advertised message from ID node B 920 b, IDnode A 920 a identifies a status flag from the message indicating IDnode B 920 b has, for example, data (e.g., sensor data 350) for upload.As a result, ID node A 920 a logs the scan result (e.g., as a type ofassociation data 340) and, when next connected to master node M1 910 a,ID node A 920 a uploads the captured scan log information to the server900. In this manner, the ID node scanning, capturing, and reportingoperations effectively create a “passive” association between thedifferent ID nodes. Such a passive association may be recorded in theserver 900 as part of association data 540.

In another embodiment, passive association between two ID nodes may beextended to an “active” association or connection. For example, withreference to the embodiment shown in FIG. 10, based upon the capturedstatus flag and uploaded information about ID node B 920 b under thatmode, the server 900 may issue a request to ID node A 920 a throughmaster node M1 910 a to actively connect or pair with ID node B 920 bfor the purpose of downloading information from ID node B 920 b. In oneexample, security credentials that authorize the active connectionbetween ID node A 920 a and ID node B 920 b are downloaded to ID node A920 a from master node M1 910 a, which received them from server 900. Inanother example, the requisite security credentials may have beenpre-staged at ID node A 920 a. And rather than rely upon an ID node toID node connection, master node M1 may have connected directly with IDnode B 920 b if M1 was within communication range of ID node B 920 b.

Information Query ID Node to Master Node Example

An exemplary ID Node may also issue queries to other nodes, both masternodes and ID nodes. FIG. 11 is a diagram illustrating exemplarycomponents of a wireless node network during an exemplary ID-to-masternode query in accordance with an embodiment of the invention. Referringnow to FIG. 11, a similar group of nodes as shown in FIG. 9 appears,except that exemplary master node M1 910 a is in an advertising orbroadcasting mode (e.g., M1 _(adv)) while ID node A 920 a is in ascanning mode (e.g., A_(scan)). In this configuration, ID node A 920 amay query master node M1 910 a for information. In one embodiment, thequery may be initiated through the ID node setting its status flag. Therequested information may be information to be shared, such as a currenttime, location, or environmental information held by the master node M1910 a.

In a passive association example, ID node A 920 a in A_(scan) mode mayhave captured the address of master node M1 910 a. However, since an IDnode cannot directly connect to the server 900 to request pairingsecurity credentials (e.g., security pin information that authorizes anactive connection between ID node A 920 a and master node M1 910 a), apassive association and corresponding pairing will have been initiatedfrom the master node. In another example, it may be possible for ID nodeA 920 a to have the pairing credentials stored as security data 335 froma previous connection. This would allow ID node A 920 a then to initiatethe active association with master node M1 910 a after a passiveassociation.

Alert Level Advertising Example

As previously noted, a node may enter an alert stage or level in one ormore embodiments. For example, if a node has not received anacknowledgement from a master node for an advertising packet within aset period (e.g., an Alert Interval as described in some embodiments),the node will enter a particular alert stage for more specializedadvertising so that it may be “found” or pass along information. FIG. 12is a diagram illustrating exemplary components of a wireless nodenetwork during an exemplary alert advertising mode in accordance with anembodiment of the invention. Referring now to FIG. 12, a similar groupof nodes as shown in FIG. 9 appears, with the addition of another masternode (master node M2 910 b) and another ID node (ID node B 920 b).Exemplary ID node A 920 a is in an advertising or broadcasting mode(e.g., A_(adv)) while nodes M1, M2, and B are each in scanning mode(e.g., M1 _(scan), M2 _(scan), and B_(scan)). In this example andconfiguration as shown in FIG. 12, the status flag in an advertisingmessage from ID node A 920 a has been set to a particular alert level(e.g., Alert Level 2) in the header of the message, requesting anynearby master node to acknowledge it. In one example, this mode may beentered if ID node A 920 a has not connected with another node for a setperiod or time. In another example, ID node A 920 a may enter thisspecialized advertising mode upon received instructions (e.g., fromserver 900 or another nearby node) or a triggered condition (other thantime), such as when a sensor input (such as light) is detected orotherwise registered and the node issues continuous updates of itsaddress as a security feature. The ID node A 920 a set at this alertlevel and in this specialized advertising mode is thus set in an activepairing mode, waiting for pairing credentials.

From a passive association perspective, any node in scanning mode canpassively associate with such an advertising node (e.g., ID node A 920 ain this alert mode). Thus, in an embodiment, the Alert Level 2 statusflag in the advertising header broadcast by ID node A 920 a indicatesthat urgent and active intervention is requested, rather than merelypassively associate without an active connection.

From an active association perspective, any node that uploads thespecial advertising header of ID node A 920 a may be forwarded thesecurity credentials from the server 900. This would allow for the nodereceiving such credentials to actively associate or pair with ID node A920 a.

While FIG. 8 provides examples of how a node may advertise, and FIGS.9-12 provide examples of how different exemplary devices (e.g., IDnodes, master nodes, and a server) may advertise and associate indifferent ways, FIGS. 22A-C provide a progressive set of illustrationsthat expand upon how associating and disassociating may be appliedwithin an exemplary wireless node network. More specifically, FIGS.22A-C show how associations and disassociations may occur when anexemplary ID node is tracked and managed by a server and differentmaster nodes as the ID node moves through an exemplary transit path inaccordance with an exemplary embodiment of the invention.

Referring now to FIG. 22A, a structure 2200 is shown having an entry andexit point. In one example, the structure 2200 may be a corridor oranother part of a building or facility. In another example, structure2200 may be a conveyor system that transports an item and its ID nodefrom the entry point to the exit point. Master node M1 2210 a is locatednear the entry point of structure 2200 while master node M2 2210 b islocated near the exit point. Those skilled in the art will appreciatethat other master nodes may be disposed at additional points instructure 2200, but are not shown for sake of convenience and tosimplify the association hand-off explanation that follows. Server 100is operatively connected to each of master node M1 2210 a and masternode M2 2210 b via network 105.

In one embodiment, server 100 has access to context data 560 related tothe structure 2200, such as layout data 585 on dimensions and materialsmaking up structure 2200. Context data 560 may include historic data 575on how an ID node has operated and successfully been tracked as ittraverses structure 2200 from the entry point to the exist point. Forexample, server 100 may have context data indicating structure 2200 is aconveyor that can transport an item and its ID node from the entry pointto the exit point over a distance of 800 feet. The context data mayfurther indicate typical items are moved at a certain speed on theconveyor of structure 2200 and a nominal time from the entry point tothe exit point may be about 5 minutes. Thus, the server 100 has accessto context data about the environment within with an ID node isoperating and may leverage this to better and more accurately manage theID node.

In FIG. 22A, ID node A 2220 a is shown entering the structure 2200 atthe entry point. Here, ID node A 2220 a may be advertising in hopes ofconnecting with a master node as it enters structure 2200 with, forexample, a non-connectable interval of 10 seconds with a connectableinterval of 5 seconds. In this example, the server 100 knows that IDnode A 2220 a is located near the entry point and anticipates that IDnode A 2220 a should be coming near to master node M1 2210 a at theentry point. Thus, server 100 may set the connectable andnon-connectable intervals accordingly so as to provide a sufficientopportunity for ID node A 2220 a to connect to the next master nodealong the predicted path of the ID node and in accordance with the speedof travel.

Additionally, server 100 may set the alert interval to 1 minute in thiscontext. Here, if ID node A 2220 a is not connected to another nodewithin 1 minute, ID node A 2220 a may broadcast or advertise with amessage having a changed status flag that indicates an alert status sothat ID node A 2220 a can connect to a broader range of other nodes thatsee it is urgent for ID node A 2220 a to connect and, essentially, befound. Depending on the context (e.g., the type of conveyor, the speedof the conveyor, the density of nodes near the entry point, etc.), thoseskilled in the art will appreciate that the server 100 can adjust theadvertising cycle intervals to better accommodate the ID node's currentenvironment.

When master node M1 2210 a is scanning (listening), it may initiallydetect an advertising packet from ID node A 2220 a during node A'snon-connectable interval. But when ID node A 2220 a changes advertisingstates and broadcasts as a connectable node in the general advertisingstate (i.e., during the connectable interval), master node M1 2210 a mayrespond with a SCAN_REQ that acknowledge receipt of the broadcastedmessage and asks for further information from ID node A 2220 a. Masternode M1 2210 a receives the requested information from ID node A 2220 a,and then communicates with the server 100 to notify the server of itspassive association with ID node A 2220 a. Server 100 determines ifactive association is desired, and may authorize the active associationbetween master node M1 2210 a and ID node A 2220 a by sending securitycredentials to master node M1 2210 a, which allow the nodes to securelyconnect and share information. And master node M1 2210 a may determinethe location of ID node A 2220 a (or server 100 may do so by directingmaster node M1 and/or ID node A), and provide the location of ID node A2220 a to server 100. Thus, server 100 is able to manage and track thelocation of ID node A 2220 a as it enters structure 2220 via at leastassociation.

In FIG. 22B, ID node A 2220 a has traversed down part of the transitpath through structure 2200 while remaining associated with master nodeM1 2210 a. However, at some point master node M1 2210 a and ID node A2220 a are disassociated at the direction of server 100 (or when theycan no longer communicate). In one example where ID node A 2220 a is onthe conveyor within structure 2200, server 100 may instruct ID node A2220 a to go to a low power mode for a particular period of time inorder to, for example, conserve ID node power. In another example, thelow power mode may also provide better location accuracy. As the server100 has access to the context data, the server 100 may know that ID nodeA 2220 a was associated with master node M1 2210 a near the entry pointat a given time, and determine that ID node A 2220 a will not be nearthe exit point until the end of the particular period of time. With theID node A 2220 a programmed this way, once the particular periodelapses, the ID node A 2220 a should be near the exit point and mayagain be placed into a normal operation mode so that it can seek toconnect with master node M2 2210 b.

Similar to the association process discussed with respect to ID node Aand master node M1, ID node A 2220 a and master node M2 2210 b may beassociated as ID node A 2220 a approaches master node M2 2210 b near theexit point. Once connected, the node locations and association data areupdated on the server 100. And as ID node A 2220 a continues to movethrough structure 2200, ID node A 2200 a may arrive at the exit point asshown in FIG. 22C, where the node locations and association data areupdated once again on the server 100.

Those skilled in the art will appreciate how such principles may beapplied to further movements of an ID node as it is handed off (e.g.,via active/passive associations and disassociations) between othermaster nodes and keeping track of these associations and node locationson the server 100. Additionally, as server 100 tracks and monitorsassociations, disassociations, and contextual environmental operations,server 100 essentially learns how to better use context informationbetter track nodes, manage power used by ID nodes, and enhance accuracyfor locations.

Those skilled in the art will also appreciate the general tradeoff witha level of RF power level and accuracy of location. If a node's RF powerlevel is set high, it may advertise and connect with other nodes alonger distance away. But at such a high power level setting, theability for the system to discriminate between and locate differentnodes may be a challenge.

Association Management within a Wireless Node Network

As explained above in general, management of nodes may rely uponassociations created and tracked between nodes. In some embodiments, theassociation relied upon may be an active association where the serverexpressly authorizes an active connection between nodes. In otherembodiments, the association relied upon may be a passive associationwhere the master node (a type of managing node) is associated with theother node, but not actively connected to the other node. By virtue ofthe passive association, the server may be able to keep track of andmanage the other node without requiring an active association. Thus,those skilled in the art will appreciate that in still otherembodiments, associations relied upon by the server for managing awireless node network may include both active and passive associationsand may be generally authenticated or, more specially, authorize asecure connection that has a degree of protection for the connection andcommunications using that connection.

FIGS. 23-25 provide flow diagrams of exemplary methods for associationmanagement of a wireless node network having at least a plurality ofnodes and a server in accordance with different embodiments of thepresent invention involving active and passive association examples.Those skilled in the art will appreciate that each of these exemplarymethods for association management of a wireless node network may beimplemented by instructions stored on a non-transitory computer-readablemedium, which when executed perform the steps of the respective methodsdescribed below (e.g., methods 2300, 2400, and 2500) and the describedvariations of those methods.

Referring now to FIG. 23, method 2300 begins by identifying a first nodeas a potential for actively associating with a second node at step 2305.In one example, identifying the nodes for association may involvereviewing a message sent by the first node to determine statusinformation related to the first node, and analyzing the statusinformation to determine whether the first node should be associatedwith the second node. In a further example, the status information maycomprise one of a plurality of different status levels indicatingwhether the first node is requesting a connection to the second nodewhen at that particular status level.

Next, an association request is transmitted to the server in step 2310.In one example, the association request may identify the first node andsecond node to be associated and may request transmission of one or moreappropriate security credentials (e.g., PIN credentials, securitycertificates, keys, and the like) that may be used by the nodes toenable the first and second node to securely connect and share data aspart of associating. An embodiment may request only one credential as anauthorization credential from the server. Other embodiments may use twocredentials where one may be later uses as a credential with which toreply to challenges. For example, if an ID node is challenged, the IDnode may send a reply authorization credential so that the master nodecan confirm the response and supply the ID node with the appropriatesecurity credential for the authorized association. In some cases, an IDnode may have been supplied with such a reply authorization credential(also generally referred to as a key) by the server.

At step 2315, the second node receives a permissive response from theserver related to the association request. In an example, the permissiveresponse may include receiving a first authorization credential and asecond authorization credential from the server (which may be stored onthe nodes). As such, the first authorization credential and the secondauthorization credential may be created by the server as a type ofsecurity data, and may be provided to authorize connecting the firstnode and the second node and securely sharing information between thefirst node and the second node.

With this authorization from the server, the first node and second nodemay be associated at step 2320. In one example, the method 2300 mayassociate the nodes by establishing an authorized connection from thesecond node to the first node based upon the authorization credential.And the method 2300 may securely provide shared data between the firstnode and the second node according to a profile established by theserver after the first and second nodes are associated.

In an embodiment, the method 2300 may also comprise having the secondnode gaining responsibility for a task after the second node isassociated with the first node when responsibility for the task waspreviously with the first node. For example, when the second node ispowered by an external power source and the first node is powered by abattery, this may advantageously shift the responsibility to a node thatis better suited to perform the task (e.g., has more power available orhas a power source that does not need recharging or replacing).

FIG. 24 is a flow diagram illustrating another example method forassociation management of a wireless node network in accordance with anembodiment of the invention from the perspective of the server.Referring now to FIG. 24, method 2400 begins with the server receivingan association request sent from a second of the nodes at step 2405. Theassociation request asks for permission to associate a first of thenodes to the second node.

At step 2410, the server determines a location (actual or relative) ofthe first node and second node. In one embodiment, the server mayreceive location data for the second node. For example, when the secondnode is a master node, the location data for the second node may be GPScoordinates for the current location of the master node, which providesthis to the server. And in an embodiment, the server may determine alocation of the first node using at least one of a plurality of locationmethods available to the server for locating the first node, such asthose discussed in detail above (or a combination of such methods sothat a more refined location of the first node is determined).

At step 2415, the server determines if associating the first node to thesecond node is desired based at least upon the location of the firstnode and the location of the second node. In one embodiment, it may bedetermined if associating is desired by determining if associating thefirst node to the second node is anticipated based upon context data. Inanother embodiment, it may be determined if associating is desired byidentifying a current mode of filtering that limits potential nodes tobe associated, and granting the permission to associate the first nodeto the second node only if the current mode of filtering allows thefirst node to be associated with the second node. For example, this mayinvolve granting the permission only if the current mode of filteringdefines that the second node is within a locational range of the firstnode consistent with the current mode of filtering. This may be definedby a particular filtering mode, such as a local, regional, or globalfiltering mode that operates to restrict nodes that may associate withother nodes. As such, the method may alter the current mode of filteringto another mode of filtering that allows the first node to be associatedwith the second node as a sort of override of the current filtering mode(e.g., depending upon an alert status of the first node).

At step 2420, the server records new association data if it is desiredto associate the first node with the second node at step 2420. At step2425, the server transmits a response to the second node granting thepermission to associate the first node to the second node. In anembodiment, the server may first generate an authorization credentialthat authorizes connecting the first node and the second node andsharing information between the first node and the second node. This maybe by looking up the credential information or by going through aprocess to create specific an authorization credential that allows thetwo nodes to actively pair and share data. With the authorizationcredential, the server may transmit them as the response.

In another example, the server may have pre-staged an authorizationcredential related to the second node and a third node if the serveranticipates the second node will disassociate with the first node andlater request to associate with the third node. For example, this may bedone if the context indicates the second node (e.g., a master node) maybe placed in a container and need to connect with the third node in thefuture when the second node may lose its connection to the server.

Method 2400 may also include the server receiving shared data from thesecond node. The shared data may originate from the first node or mayhave parts that originate from both the first and second nodes. Forexample, the second node may have received the permission to associate,and actively paired with the first node in a secure manner. The firstnode may have indicated it has data to upload (e.g., sensor data), andthe second node may receive the data from the first node. Subsequent tothat sharing, the second node may upload the shared sensor data from thefirst node by transmitting it to the server.

The method may further comprise instructing the second node to take overresponsibility for a task previously performed by the first node afterthe second node is associated with the first node. For example, when thesecond node is powered by an external power source and the first node ispowered by a battery, the responsibility for certain tasks may be takenover by the node with a more robust power supply (e.g., the node poweredby an external power source).

In more detail, the responsibility for certain tasks may be established,tracked and changed with a programmable profile. For example, in oneembodiment, the server may establish a profile for how long the taskresponsibility would change. In some cases, the profile may define aperiod of time for how long a node having this profile would haveresponsibility for a certain task before it would revert back to adefault node. In another example, a node (such as a master node) mayhave a default condition trigger (like a low power situation or when itcannot communicate with the server) that can override such a profile sothat it does not take on more responsibilities under particularconditions.

Furthermore, an embodiment may have the master node deciding what othernode may take on responsibility for certain tasks. This may be helpfulin situations where access to the server may be limited (e.g., anairborne environment). However, managing such a profile may be moreeasily accomplished in other embodiments with easier access to moretypes of context data on the server level.

In an embodiment that implements association management as a system,such an exemplary system for association management of a wireless nodenetwork may comprise a first node, a second node, and a server. Thesecond node includes a node processing unit, a node volatile memorycoupled to the node processing unit, a first communication interfacecoupled to the node processing unit, and a second communicationinterface coupled to the node processing unit. The first communicationinterface provides a short-range communication path between the firstnode and the second node and the second communication interface providesa longer range communication path between the second node and theserver.

The server includes a server processing unit, a server volatile memorycoupled to the processing unit, and a third communication interface thatprovides a longer range communication path between the server and thesecond communication interface of the second node.

The node volatile memory maintains at least a first program code section(e.g., master control and management code 425 or parts thereof) whilethe server volatile memory maintains at least a second program codesection (e.g., server control and management code 525 or parts thereof).

When executing the first program code section resident in the nodevolatile memory, the node processing unit of the second node isoperative to identify the first node as a potential for associating withthe second node, transmit an association request over the secondcommunication interface to the server, receive an association response(having at least authorization information generated by the server) overthe second communication interface from the server, provide theauthorization information to the first node, and associate the firstnode and the second node.

In one example, the node processing unit may be further operative toreview status information related to the first node to determine whetherthe first node desires association with the second node. In anotherexample, the node processing unit may be further operative to securelyprovide shared data between the first and second node after the firstand second node are associated and in accordance with a sharing profileprovided by the server. The sharing profile may define types ofinformation to be securely shared between particular nodes.

When executing the second program code section resident in the servervolatile memory, the server processing unit is operative to determine alocation of the first node and second node, determine if associating thefirst node to the second node is desired based at least upon thelocation of the first node and the location of the second node, storenew association data in the server volatile memory if it is desired toassociate the first node with the second node, and transmit theauthorization response to the second node granting the permission toassociate the first node to the second node.

In one embodiment, the second node in the system may take overresponsibility of a task previously handled by the first node after thesecond node is successfully associated with the first node. For example,when the second node is powered by an external power source and thefirst node is powered by a battery, the system may be more effectivelyand efficiently managed by reassigning a task (especially a task thatinvolves a significant expenditure of power, a series of operations overa significant period of time, or both) to another node, such as thesecond node, which has more power available than the first node.

In another embodiment, the server processing unit may be furtheroperative to set a current mode of filtering that limits potential nodesto be associated, and grant the permission to associate the first nodeto the second node only if the current mode of filtering allows thefirst node to be associated with the second node. In a furtherembodiment, the server processing unit may be further operative to alter(e.g., override) the current mode of filtering to a different mode offiltering. In this way, the server may adapt how nodes are managed andallow the first node to be associated with the second node if it isdesired, such as then the first node is in an alert status level andurgently is requesting connection to a larger group of nodes thanpermitted under the current mode of filtering.

While the exemplary methods illustrated in FIGS. 23 and 24 focus onactive associations, FIG. 25 is a flow diagram illustrating an examplemethod for association management of a wireless node network having atleast a plurality of nodes and a server in accordance with anembodiment, but from the perspective of a node that is to be passivelyassociated with another node. Referring now to FIG. 25, method 2500begins with a second of the nodes receiving a message broadcasted from afirst of the nodes at step 2505. At step 2510, the second node capturesan address of the first node from the message. At step 2515, the firstnode and the second node are associated by storing the captured addressof the first node and an address of the second node as association datain a memory of the second node. At step 2520, the second node transmitsthe association data to the server.

At some point, the server may be updated by the second node with updatedassociation data when the second node does not receive an additionalmessage broadcast from the first node. For example, the second node andthe first node may stay associated and securely connected for a periodof time, but eventually the first node may move such that the connectionis no longer viable or the first node may move closer to another nodealong the anticipated path it is traveling (e.g., an anticipatedshipping path along a conveyor within a structure from an entry point ofthe structure but now closer to an exit point of the structure). As thefirst node travels on the conveyor, it may get closer to another nodenear the exit point and is better managed by an association with thatother node near the exit point. Thus, the updated association datareflects that the first node is disassociated from the second node.

Method 2500 may further include having the second node determining alocation of the first node, and updating the server with a currentlocation of the second node and the determined location of the firstnode. Additionally, method 2500 may include receiving locationinformation from the server that defines a refined location of the firstnode.

In an embodiment that implements passive association management as amanaging node (e.g., a master node) in a wireless node having at leastanother node and a server, such an exemplary managing node comprises aprocessing unit, a first and second communication interface each coupledto the processing unit, a volatile memory coupled to the processingunit, and a memory storage coupled to the processing unit. The firstcommunication interface provides a first communication path to the othernode, can receive a message broadcast from the other node, and providethe message to the processing unit. The second communication interfaceproviding a second communication path to the server.

The memory storage may maintain at least a node association managermodule as program code to be executed by the processing unit. When theprocessing unit loads the module into volatile memory and executesinstructions of the module, the processing unit is operative to receivethe message from the first communication interface, capture an addressof the another node from the message, store the captured address of theanother node and an address of the managing node as part of associationdata in the memory storage, and transmit the association data to theserver through the second communication interface.

In one example, the memory storage also maintains a location managermodule and, when the processing unit also loads the location managermodule into volatile memory and executes instructions of that module,the processing unit is operative to determine a location of the othernode, determine a current location of the managing node (e.g., via GPSlocation signals), and update the server with the current location ofthe managing node and the determined location of the other node.

The managing node may be further operative to update the server withupdated association data when the first communication interface does notreceive an additional message broadcast from the other node. The updatedassociation data may reflect that the other node is disassociated fromthe managing node.

Context Management within a Wireless Node Network

As explained above in general, management of nodes may rely upon thecontextual environment of the nodes. As shown in FIG. 5, server 100 hasaccess to a wide variety of different context data 560. Context data,such as data 560, may include a wide variety of data that generallyrelates to the environment in which the nodes are operating and may beused to advantageously provide enhanced node management capabilities inaccordance with embodiments of the present invention. As such, the useof such context data provides a data foundation in an embodiment so thatthe server may better and more efficiently implement management tasksrelated to nodes in the network, and adjust such tasks to account forrelevant context data as nodes move within the network (e.g., as an IDnode moves with an item being shipped along an anticipated or predictedtransit path from an origin to a destination). For example, the servertake advantage of its ability to rely upon relevant context data toadvantageously alter how it instructs a node operate, how it associatesa node with the another node, how it can better locate a node, and howit can more efficiently track and respond to requests to report thelocation of the node.

FIG. 26 is a flow diagram illustrating an exemplary method for contextmanagement of a wireless node network in accordance with an embodimentof the invention. Referring now to FIG. 26, method 2600 begins at step2605 by identifying, by the server, at least one of the nodes. In oneexample, such as that shown in FIG. 22a , server 100 may identify IDnode A 2220 a as part of communications received from master node M12210 a. At step 2610, the server determines context data that relates toan operating environment of the identified node as the identified nodemoves within the operating environment.

In one embodiment, the context data may include one or more types ofdata, such as scan data, historic data, shipment data, RF data, andlayout data. For the example shown in FIG. 22a , server 100 may accesscontext data 560 (which may be kept in context database 565) todetermine parts of the context data 560 that relate to the operatingenvironment of ID node A 2220 a. Such context data 560 may include, inthis example, shipment data that relates the item being shipped that isconnected to ID node A 2220 a, scan data for when the item connected toID node A 2220 a was scanned upon entering structure 2200, historic datafor how long it takes a node to traverse the conveyor located withinstructure 2200, and layout data on dimensions of structure 220. Thoseskilled in the art will appreciate that context data may includeoperational environment information created within the wireless nodenetwork or created by a third party (e.g., weather information relatedto the operating environment of ID node A 2220 a).

While the server determines context data that relates to an operatingenvironment of the identified node in one embodiment, such a current oranticipated operating environment for a node in a more detailedembodiment may include one or more types of environments. For example,the current or anticipated operating environment for a node may includean electronic communication environment, a physical environment of ananticipated path along with a node moves, a conveyance environmentrelated to how a node moves, and a density environment related to thedensity of nodes within an area near a particular node identified by theserver.

Back at step 2610, the determining step may involve determining thecontext data that relates to an anticipated operating environment of theidentified node as the identified node moves in a predicted path towardsa location of another node. In another example, the determining step mayinvolve determining the context data that relates to the anticipatedoperating environment of the identified node and an anticipatedoperating environment of the another node as the identified node movesin the predicted path towards the another node for an expectedassociation with the another node

At step 2615, the server performs a management task related to theidentified node with an adjustment made to account for the determinedcontext data. When the determined context data (such as RF signaldegradation information) indicates that no adjustment is actually neededwhen performing the task, no adjustment is made given the determinedcontext data. Thus, those skilled in the art will appreciate that anadjustment may be made when needed contextually and is not required atall times.

In one embodiment, performing the management task may comprise generallyinstructing the identified node to alter its operation based upon thedetermined context data. For example, server 100 may perform themanagement task of instructing ID node A 2220 a to change itsconnectable and non-connectable intervals as it approaches master nodeM1 (which server 100 knows from context data, such as scan datagenerated when node A entered structure 2200). Thus, in this example,server 100 is able to leverage enhanced visibility of ID node A 2220 abased upon context data and advantageously alter the operation of node Ato increase the node's chance of successfully associating with masternode M1 2210 a.

In other embodiment, performing the management task may compriseassociating the identified node with another node with the adjustmentmade to alter an associating parameter based upon the determined contextdata. In other words, context data may be helpful as part of associatingnodes. In one example, the associating parameter may include at leastone altered timing interval related to associating the identified nodewith the other node, such as an alert interval or connectable interval.These intervals are parameters that may be altered as part ofadjustments made when a server associates two nodes and, for example,sets the intervals to more appropriate time durations in order toenhance the chance and opportunity the nodes have to actively pair andsecurely share data as needed.

In yet another embodiment, performing the management task may compriselocating the identified node with an adjustment made to a power settingbased upon the determined context data. In one example, the powersetting adjustment is done to a master node in direct communication withthe server. In another example, the power setting adjustment may be doneto an ID node, which is passed this operational adjustment informationfrom another node. In one embodiment, the power setting itself maycomprise an output power level adjusted to account for an adversecondition in the operating environment of the identified node (e.g., amaster node with an adjusted RF output signal level). The adversecondition may be, for example, an adverse RF communication environmentwhere structure attenuates or otherwise impedes normal RFcommunications. In another example, the adverse condition may be ahighly dense population of nodes close to the identified node.

In more detail, the output power level may be adjusted to account for ashielding condition in the operating environment of the first node. Sucha shielding condition may be caused, for example, by one or more ofpackaging, package contents, proximate package, proximate packagecontents, and physical infrastructure in the operating environment ofthe first node. For example, if the identified node is located near ametal container, it is operating in an adverse RF communicationsenvironment where it may have its output power level increased based onthis context data in order to better deal with the adverse shieldingcondition.

In still another embodiment, performing the management task may compriseproviding the location of the identified node in response to a requestreceived by the server related to a status of the identified node. Forexample, if server 100 receives a request from user access device 205about the status of ID node A 2220 a, server 100 is able to provide thelocation of node A as being within structure 2200, but refined as beingclose to the entry of the structure given the adjustment to account forcontextual data, such as scan data related to the item being shippedwith node A 2220 a.

Those skilled in the art will appreciate that method 2600 as disclosedand explained above in various embodiments may be implemented on aserver, such as server 100 illustrated in FIGS. 5 and 22A, running oneor more parts of server control and management code 525 (e.g., thecontext based node manager). Such code may be stored on a non-transitorycomputer-readable medium such as memory storage 515 on server 100. Thus,when executing code 525, the server's processing unit 500 may beoperative to perform algorithmic operations or steps from the exemplarymethods disclosed above, including method 2600 and variations of thatmethod.

Node Location Determination Methodologies

As part of managing and operating a wireless node network in accordancewith one or more embodiments of the invention, such as tracking ID nodeA 2220 a in FIGS. 22A-C, determining a node's location is performed. Asexplained above, an exemplary ID node may be directly or indirectlydependent on a master node to determine its location. In the embodimentsdiscussed and described herein, a location of a node may generallyencompass a current or past location. For example, an embodiment thatdetermines a node's location may be a current location if the node isnot moving, but may necessarily determine the location as a pastlocation should the node be in a state of motion.

Likewise, the term location alone may include a position with varyingdegrees of precision. For example, a location may encompass an actualposition with defined coordinates in three-dimensional space, but use ofthe term location may also include merely a relative position. Thus, theterm location is intended to have a general meaning unless otherwiseexpressly limited to a more specific type of location.

Determining node location may done by a master node alone, the serveralone, or the master node working together with the server. And on suchdevices, embodiments may use one or more methodologies to determine anode's location and further refine the location. Such examplemethodologies may include, but are not limited to, determining nodelocation may relate to controlling an RF characteristic of a node (e.g.,an RF output signal level and/or RF receiver sensitivity level),determining relative proximity, considering association information,considering location adjustments for context information and an RFenvironment, chaining triangulation, as well as hierarchical andadaptive methods that combine various location methodologies. A moredetailed description of these exemplary node location determinationtechniques is provided below.

Location through Proximity

In one embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes. If neithernode's actual location is known, one embodiment may infer a locationrelationship of the two nodes through proximity.

Proximity when Varying Power Characteristics

For example, an exemplary method of determining a node's location in awireless node network of nodes may involve varying a node's powercharacteristic, such as the output power of one of the nodes. Generallyand as explained with reference to FIG. 13, the power characteristic maybe varied to identify closer ones of the nodes to the node broadcasting.The node broadcasting may transmit one or a series of signals whileother nodes may report receiving one or more of the signals. Those othernodes that receive at least one signal broadcast from the transmittingnode may be deemed part of a close group of nodes. And as the powercharacteristic is varied (increased or decreased or both), a closestgroup of nodes (or single node) may be identified as the smallest groupof nodes of those that receive at least one signal from the broadcastingnode. Accordingly, while not absolute, a type of location for thebroadcasting node may be determined based on the closest one or group ofnodes. This may be repeated for neighboring nodes to yield a set ofclosest node information for each of the nodes. In more detail, anexemplary set of closest node information for each of the nodes mayinclude which nodes are closest (via the lowest power characteristic)and more robustly supplement this information with which other nodes areincrementally further away (via increasingly larger powercharacteristics). Thus, the set of closest node information provides thebasis for a determination of how close the nodes in the network are toeach other, which provides a type of location determination for eachnode.

Additionally, context data may be referenced in certain embodiments tofurther enhance determining how close the nodes are to each other. Forexample, combining the set of closest node information with contextdata, such as scan information that registers when an item changescustodial control in a delivery system, may further refine how todetermine the location of the nodes. Scan and other context informationwill help determine if one or more of the nodes, for example, are knownto be in the same container, vehicle or moving on a belt together. Thus,this type of context data may be integrated into a further step ofrefining how close the nodes are to each other based upon the contextdata.

In general, a location of a node based upon proximity may be determinedwhen a power characteristic of nodes is changed or varied in a wirelessnode network. FIG. 28 is a flow diagram illustrating an exemplary methodfor location determination by varying a power characteristic of nodes ina wireless node network in accordance with an embodiment of theinvention. Referring now to FIG. 28, method 2800 begins by at step 2805by instructing a first of the nodes to vary the power characteristic forone or more signals broadcast by the first node. In a more detailedembodiment, such an instruction may cause the first node, for example,to incrementally decrease or incrementally increase the powercharacteristic (such as an output power level) between values.

At step 2810, method 2800 continues by identifying a first group ofother nodes in the wireless node network that are near the first nodebased upon those of the other nodes that received at least one of thesignals broadcast by the first node as the first node varies the powercharacteristic. In a further embodiment, step 2810 may incrementallyidentifying which of the first group of other nodes are receiving atleast one of the broadcast signals as the first node incrementallyvaries the output power level of the signals broadcast. Theincrementally identified nodes may be deemed a set of increasingly closenodes to the first node.

At step 2815, method 2800 continues by identifying a closest one or moreof the other nodes as a smallest group of the other nodes that receivedat least one of the one or more signals broadcast by the first node asthe first node varies the power characteristic.

At step 2820, method 2800 concludes by determining a location of thefirst node based upon the closest one or more of the other nodes. Thus,as the power characteristic is varied, the group of nodes that havereceived at least one of the signals broadcast by the first node maychange and the smallest such group being a closest group of nodes (evenif just one node) to the first node. In a more detailed embodiment, step2820 may comprise determining the location of the first node based uponthe closest one or more of the other nodes and the set of increasinglyclose nodes to the first node as the set of increasingly close nodesprovides more detailed proximity information for a refined locationdetermination.

For example, referring to FIG. 14, the set of increasingly close nodesto the ID node F 920 f may include node M3 as being farthest away and M1being closer than M3. When the power characteristic of ID node Fincrementally decreases, and its output power level changes from P1 toP2, M3 can no longer receive the signal, but M1 and M2 still do. And asthe power characteristic of ID node F continues to incrementallydecrease, and its output power level is changed from P2 to P3, M1 can nolonger receive the signal, but only M2 does as the last of the nodesclosest to ID node F. Thus, in this example, determining the location ofID node F may be based upon the fact that M2 is the closest node and theset of increasingly close nodes include M1 and M3 with M1 being closerthan M3.

In another embodiment, one or more further refinements to the firstnodes location may be performed. In one example, steps 2805-2820 may berepeated where a second of the nodes is instructed to vary the powercharacteristic for one or more signals broadcast by the second node, andthen method 2800 may further refine the location of the first node basedupon a location of the second node. In a more detailed example, steps2805-2820 may be repeated where a second of the nodes is instructed tovary the power characteristic for one or more signals broadcast by thesecond node, and then method 2800 may further the location of the firstnode based upon a location of the second node and a set of increasinglyclose nodes to the second node. With this increasingly cross-relatedinformation on what nodes are closer to other nodes and to what degree,which may be further repeated for additional nodes, embodiments mayfurther refine the location of the first node within the network.

Method 2800 may further include determining context data related to thefirst node, and refining the location of the first node based upon thecontext data. In an embodiment where the power characteristic is outputpower level, the incremental changes in the output power level of thebroadcast signal in steps 2805-2815 may be set according to the contextdata.

Method 2800 may also determine the context data to be related to theclosest node to the first node, and refine the location of the firstnode based upon the context data. In still another example, method 2800may determine the context data to be related to the incrementallyidentified nodes in the set of increasingly close nodes to the firstnode, and refining the location of the first node based upon the contextdata. For example, the closest node and the set of increasingly closenodes may have scan data that indicate they are within the samecontainer. This exemplary context data may be used to further refine thelocation of the node being located, which may help efficiently determinethat node is near the container. As such, those skilled in the willappreciate that context data for the node being located as well as nodesidentified to be close to that node may provide relevant input toadvantageously help further refine the location of the node.

Those skilled in the art will appreciate that method 2800 as disclosedand explained above in various embodiments may be implemented on aserver apparatus, such as server 100 illustrated in FIGS. 5 and 22A,running one or more parts of server control and management code 525(e.g., the location manager). Such code may be stored on anon-transitory computer-readable medium such as memory storage 515 onserver 100. Thus, when executing code 525, the server's processing unit500 may be operative to perform algorithmic operations or steps from theexemplary methods disclosed above, including method 2800 and variationsof that method.

An embodiment of such a server apparatus may include a server (such asserver 100) operative to communicate with a plurality of nodes in thewireless node network. As explained with respect to FIG. 5, the servergenerally includes a server processing unit, a server volatile memory, aserver memory storage, and at least one communication interface. In thisembodiment, the volatile memory, memory storage, and communicationinterface are each coupled to the processing unit. The memory storagemaintains at least a program code section and location data related to alocation of one or more of the nodes. The communication interfaceprovides a communication path operatively coupling the server with thenodes.

The server processing unit, as mentioned above, is operative whenrunning the program code section, to perform the steps and operations asdescribed above relative to method 2800 and variations of that methoddescribed above.

Proximity when Observing Signal Patterns and Strengths Over a TimePeriod

In another embodiment, an improved method for determining a node'slocation through proximity may include analyzing the signal patterns andstrengths between an advertising node and a listening node. In oneembodiment, a threshold may be set for association based on an observedmessage count and/or recorded signal strength within a specific timeperiod may improve the ability to locate a node (e.g., an ID node) tothat of another node (e.g., a master node). In some embodiments, theobserved message count may be implemented as an averaged count over arepeated time periods. Further still, other embodiments may filteroutlying observations in the observation data set to help improve thequality of data relied upon for setting a threshold for association and,as a result, determine a node's location.

In a more detailed example, an improved method for determining a node'slocation through proximity may show captured advertising message countsas a component for a node's location and determining a node's directionof travel. In this example, two exemplary master nodes (e.g., masternode M1 910 a and M2 910 b) may capture advertising messages from one IDnode (e.g., ID node A 920 a). Master node M1 may observe and capture(e.g., record information related to the observation) 60 messages fromID node A within a 2 minute period, while master node M2 only observesand captures 7 advertising messages from ID node A within that sameperiod. Based upon the difference in how often messages are observedfrom ID node A by master node M1 compared to those observed by masternode M2, the system is able to determine that ID node A would moreproximate to master node M1, and it's known location.

In a further embodiment, comparing the average time stamp of thecaptured records may allow the system can make a more accuratedetermination of location. For example, if the average captured messagefound on master node M2 is increasingly growing larger (e.g., takinglonger for messages to go from ID node A to master node M2), thisindicates ID node A is moving away from master node M2. If the averagecaptured message found on master node M2 is growing increasingly largerwhile the average captured message found on master node M1 isincreasingly growing smaller, this indicates ID node A is moving awayfrom master node M2 and toward master node M1. Thus, over a number ofobserved time periods, the change in message timing (transmission toreception) may also be relied upon to enhance or refine a node'slocation.

In yet another embodiment, the observed signal strength may be acomponent in location determination and estimating direction of traveland may allow the system can make a more accurate determination oflocation. For example, two master nodes (M1 910 a and M2 920 b) may becapturing advertising messages from a node (ID node A 920 a). M1captures 60 messages from ID node A within 2 minutes, while M2 capturesonly 7 messages. The average signal strength observed for signals fromID node A by master node M1 is higher compared to the average signalstrength observed by master node M2. Based upon this observed signalstrength information, the system would determine that ID node A to be atM1, but a predicted path may indicate ID node A is heading towards M2.As the master nodes M1 and M2 continue to capture records, the system(e.g., management code 524 operating on server 900, which is incommunication with M1 and M2) processes the continued feed of capturerecords from M1 and M2. With this observed signal strength information,the server 900 would expect that the count and average signal strengthof messages from ID node A over the time period observed (2 minutes) toincrease for observations at M2 and to decrease for observations at M1when ID node A is physically moving closer to M2 and away from M1. Thus,the change in observed powers levels and in how often messages areobserved may indicate actual node movement in an embodiment.

Basing node proximity location and node directional determinations onobserved signal patterns and characteristic strengths over a period oftime has the advantage of reducing the likelihood of unwanted andspurious signal anomalies causing an ID node's location to beincorrectly determined. And the above exemplary methods for determiningmovement characteristics of a node (e.g., moving closer to one node,moving closer to one but away from another, etc.) as part of refiningthe node location may be applied in combination with the variousembodiments for determining node location described herein.

FIG. 27 is a flow diagram illustrating an exemplary method for proximitylocating a node in a wireless node network based upon observed signalpatterns and characteristic indications over a period of time inaccordance with an embodiment of the invention. Referring now to FIG.27, method 2700 begins at step 2705 by instructing a first and a secondother nodes to detect any message broadcast from the one node over aperiod of time. The period of time may be set based upon a variety offactors, such as context data. In more detail, the period of time may bedynamically changed based upon context data as the one node moves intodifferent contextual environments.

Method 2700 has the server receiving a first indication from the firstother node at step 2710 and receiving a second indication from thesecond other node at step 2715. Finally, the method 2700 determines alocation of the one node based upon a difference in the first indicationand the second indication at step 2720.

The first indication is related to a characteristic of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time. Likewise, the second indication is related tothe characteristic of messages broadcast from the one node that aredetected by the second other node during the period of time. Theseindications may include, for example, a count of messages received bythe respective other nodes, a transit time factor (e.g., an averagetransit time for a message to be detected after broadcast), and anaverage signal strength.

In one embodiment, the first indication may be a first count of messagesbroadcast from the one node that are detected by the first other nodeduring the period of time, and the second indication may be a secondcount of messages broadcast from the one node that are detected by thesecond other node during the period of time. As such, determining thelocation of the one node may be the location that is closer to the firstother node than the second other node when the first count is greaterthan the second count. Additionally, the method 2700 may further includedetermining an actual node movement direction for the one node basedupon comparing the first count and the second count over a plurality oftime periods. For example, the method 2700 may repeat observations overseveral of these time periods and track the first count and second countover time to determine which is increasing, which is decreasing, anddetermine movement of the one node based upon these measurements overtime.

In another detailed embodiment, the first indication may be a first timefactor of messages broadcast from the one node that are detected by thefirst other node during the predetermined time period, and the secondindication may be a second time factor of messages broadcast from theone node that are detected by the second other node during the period oftime. And an actual node movement direction for the one node may bebased upon comparing the first time factor and the second time factor.In a more detailed embodiment, the first time factor may be an averagetransit time for a message detected at the first other node to go fromthe one node to the first other node, and the second time factor is anaverage transit time for a message detected at the second other node togo from the one node to the second other node. As such, determining thelocation of the one node may be that the location is closer to the firstother node than the second other node when the first time factor is lessthan the second time factor.

In yet another embodiment, the first indication may be a first averagesignal strength of messages broadcast from the one node that aredetected by the first other node during the period of time, and thesecond indication may be a second average signal strength of messagesbroadcast from the one node that are detected by the second other nodeduring the period of time. As such, determining the location of the onenode may be that the location is closer to the first other node than thesecond other node when the first average signal strength is greater thanthe second average signal strength.

The method 2700 may also include, in an embodiment, observing a degreeof change in the first average signal strength and a degree of change inthe second average signal strength over repeated time periods, anddetermining an actual node movement direction for the one node basedupon comparing the degree of change in the first average signal strengthand the degree of change in the second average signal strength.

In another embodiment, the method 2700 may also refine the determinedlocation of the one node. In this embodiment, the method 2700 mayfurther comprise refining the location of the one node based upon atleast one of a first updated location received from the first other nodeand a second updated location received from the second other node. Forexample, when first other node is a mobile master node and it is thecloser of the two nodes to the one node being located, the embodimentcan take advantage of the location signaling onboard the first othernode that provides the current location of the first other node. Thatcurrent location data may be transmitted by the first other node to theserver to update the server in its calculation of the location for theone node.

In still another embodiment, the method 2700 may layer context data withthe determined location to refine the location of the node. Context datarelated to the one node may be determined by the server, and so thelocation of the one node may be refined based upon that context data. Inanother example, context data related to the closer of the first othernode and the second other node when compared to the location of the onenode. For example, the server may be aware that a particular master nodeis closer to the one node compared to a second master node, and that theparticular master node is within a container. With this additionalcontext data related to the particular master node, the server mayrefine the location of the one node based upon the context data. Otherexemplary types of relevant context data may be relied upon whenrefining the location of the one node, such as context data of aparticular shielding associated with the environment near the particularmaster node (e.g., a particular type of ULD having known RF shieldingcharacteristics, etc.)

Additionally, the method 2700 may involve looking to see if the one nodeis behaving as expected. More specifically, a further embodiment of themethod 2700 may further compare the location of the one node to apredicted path of the one node to determine if the one node is locatedoutside the predicted path. This may allow the server to use learned,historic data when creating a predicted path, and keep track of the onenode relative to being within an acceptable range associated with thispredicted path. The method may also generate a notification if the onenode is outside the predicted path. In this manner, actionable tasks canthen be taken to locate the one node—e.g., changing filter mode optionsfor nodes in that general area, etc.

Those skilled in the art will appreciate that method 2700 as disclosedand explained above in various embodiments may be implemented on aserver, such as server 100 illustrated in FIGS. 5 and 22A, running oneor more parts of server control and management code 525 (e.g., thelocation manager). Such code may be stored on a non-transitorycomputer-readable medium such as memory storage 515 on server 100. Thus,when executing code 525, the server's processing unit 500 may beoperative to perform algorithmic operations or steps from the exemplarymethods disclosed above, including method 2700 and variations of thatmethod.

Association Driven Locating with Variable RF Characteristics

As noted above, a signal strength measurement between two or more nodesmay be used to determine relative distance between nodes. If one of thenodes has a known location (such as master node M1 910 a), a relativelocation of one or more nodes within a range of the known location nodeis generally a function of how accurate the system may determine adistance between the node with known location and associated nodes. Inother words, an embodiment may identify a relative location of an itemand its related node by relying upon association-driven variablelow-power RF output signals to determine a distance the node is from aknown location.

Location Determination through Master Node Advertise

As generally mentioned above, determining node location may relate tocontrolling an RF characteristic of a node (e.g., an RF output signallevel and/or RF receiver sensitivity level) and, more specifically, mayinvolve aspects of controlling master node advertising. FIG. 13 is adiagram illustrating an exemplary location determination using masternode advertise in accordance with an embodiment of the invention. In theillustrated embodiment shown in FIG. 13, a master node, such as masternode M1 910 a, with a known location is broadcasting an advertisingmessage at varying RF output power levels. FIG. 13 illustrates theexemplary different RF output power levels as concentric ranges1305-1315 about master node M1 910 a. Thus, master node M1 910 a maybroadcast at a maximum power P1, related to range 1305, but may controlthe RF output power level and dynamically change the RF output powerlevel to P2 and broadcast at a smaller range 1310, or to P3 andbroadcast to an even smaller range 1315.

In the illustrated embodiment, receiving ID nodes A-E 920 a-920 e are inquery (scan) mode and can each use the received signal at differentlevels to determine how far away from the transmitting M1 they arelocated. Those skilled in the art will appreciate that while theillustrated embodiment shown in FIG. 13 has the receiving nodes all asID nodes, other embodiments may have receiving nodes be either master orID nodes or a mixture.

In the exemplary embodiment of FIG. 13, the location for nodes A-E maybe determined based upon the known location of master node M1 910 a.That location, plus a range measurement when each of respectivereceiving nodes A-E last receives a signal from node M1, and factoringin a confidence factor of the range measurement, provides a locationdetermination for the nodes according to variable RF signal power.Depending on a quality of the range measurement, the individualreceiving nodes may or may not have an individually calculated location.In yet another embodiment, if third party or context data, such as scaninformation, is available, a refined location may be determined usingsuch data as an additional confidence factor. As the communication rangeof M1 is limited from P1 to P3, the accuracy of location by associationgoes up.

In the illustrated example of FIG. 13, an exemplary method ofdetermining a node's location may be described that uses master nodeadvertising. First, when the master node M1's variable power short rangecommunication interface 480 is set to P1, its maximum output, masternode M1 910 a is seen by each of ID nodes A-E 920 a-920 e. Based uponanalytics or historic measurements, the open air performance (optimalrange) of the radio in M1's variable power short range communicationinterface 480 at P1 power level may have been previously been found tobe approximately 30 feet. Thus, without the need to examine RSSI levelsfrom the individual ID nodes A-E 920 a-920 e and without the need foractive calibration phases, the system may know that ID nodes A-E arewithin 30 feet of master node M1 910 a.

Next, when the master node M1's variable power short range communicationinterface 480 is set to P2, a medium output level in this example,master node M1 is seen by nodes A and B. From previous analytics orhistoric measurements, it was determined the open air performance(optimal range) of the master node M1's variable power short rangecommunication interface 480 running at P2 power level is approximately15 feet. Thus, without the need to examine RSSI levels from theindividual nodes, we know ID nodes A 920 a and B 920 b are within 15feet of master node M1. Furthermore, we know the ID nodes no longerreceiving the broadcasted RF signal from master node M1 910 a (e.g., IDnodes C 920 c, D 920 d, and E 920 e) are somewhere within 30 feet ofmaster node M1 910 a, but probably more than 15 feet away from M1.

And when the master node M1's variable power short range communicationinterface 480 is set to P3, its minimum output level in this example, itis seen by ID node B 920 b. From previous analytics or historicmeasurements, it was determined the open air performance (optimal range)of the master node M1's variable power short range communicationinterface 480 running at P3 power level is approximately 5 feet. Thus,without the need to examine RSSI levels from the individual ID nodes, weknow the location of ID node B 920 b is within 5 feet of the knownlocation of master node M1 910 a.

The ranging steps, as discussed in the example above, may then berepeated for any of the identified nodes in order to build a moreaccurate picture of the relative location of each node. The granularityof RF characteristic settings (e.g., the RF output signal power levelsetting) will provide more granularity of location differentiation whenperforming the ranging steps. In one embodiment, the ranging steps maybe performed over a set of gross RF characteristics settings (e.g., fewsettings over a wide range), and similar steps may then be performedover more select ranges for the RF characteristics settings.

FIG. 29 is a flow diagram illustrating an exemplary method for locationdetermination using one or more associations of nodes in a wireless nodenetwork in accordance with an embodiment of the invention. Referring nowto FIG. 29, method 2900 begins at step 2905 where a first of the nodesbroadcasts one or more first messages at a first anticipated orpredicted range distance. In one embodiment, the first anticipated rangedistance is an optimal range for the first node. For example, the firstnode's radio in its communication interface may have a maximum settingto allow the node to broadcast at maximized range assuming a clearenvironment. Such a setting provides a known anticipated range distance.In the example of FIG. 13, master node M1 910 a may be broadcasting at amaximum power level P1 that reaches a first range distance from node M1.However, if node M1 is known to be within an adverse RF shieldingenvironment, the first anticipated range distance may be a distanceadjusted to account for the contextual environment of such shielding(e.g., a type of context data). Anticipated range distances may beadjusted depending upon one or more types of relevant context (e.g., oneor more types of context data related to how an RF output signal fromthe node may be impeded).

At step 2910, method 2900 identifies which of the nodes associated withthe first node received at least one of the first messages. In oneembodiment, the first node may be able to access and review associationdata in its onboard memory storage as part of identifying which are thenodes associated with it. In one example, the associations with thefirst node may be passive associations (e.g., not actively paired andsecurely connected) or active associations (e.g., actively paired andable to securely connect and share data), or a combination of both typesof associations.

Next, at step 2915, the first node broadcasts one or more secondmessages at a second anticipated range distance, which is incrementallysmaller than the first anticipated range distance. In the example ofFIG. 13, master node M1 910 a may be the first node and now isbroadcasting at a medium power level P2 that reaches a secondanticipated range distance from node M1. By incrementally changing theRF power level in this manner, master node M1 910 a now no longer canreach nodes C-E as shown in FIG. 13.

At step 2920, method 2900 concludes by determining a location of one ormore of the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages, wherethe location is between the first and second anticipated range distancesfrom the first node. Again, in the example of FIG. 13, master node M1910 a may determine the location of nodes C-E (given they did notreceive the message sent out the second anticipated range distance at RFpower level P2) to between the first anticipated range distance (whenmaster node M1 was broadcasting at power level P1) and the secondanticipated range distance (when master node M1 was broadcasting atpower level P2) from the known location of master node M1.

In one embodiment, the method 2900 may also have the first nodebroadcasting one or more third messages at a third anticipated rangedistance (incrementally smaller range than the second anticipated rangedistance), and determining a location of one or more of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages, where the location isapproximately near the second anticipated range distance from the firstnode. Again, in the example of FIG. 13, by incrementally changing thepower level down to P1 and broadcasting a third message at ananticipated range distance for that P1 level, the master node M1 candetermine the location of node A (as node A received the second messagebut did not receive the third message) to be approximately near theanticipated range distance for P2 from the location of master node M1.

Additional embodiments of method 2900 may also refine such determinedlocations by updating the location of the first node. In one embodiment,the first node may be a mobile node. As such, refining may involvedetermining a current mobile location of the first node, and refiningthe location of the one or more of the identified associated nodes thatdid not receive any of the second messages but received at least one ofthe first messages based upon the current mobile location of the firstnode. Thus, as the first node moves and updates its own location (e.g.,via GPS signals received by location circuitry 475 on a master node),the first node is able to leverage its own updated location andadvantageously refine the location of nodes associated with it.

And, in some embodiments, the refined location of associated nodes maybe transmitted to a server. This provides an update to the server, andaids in tracking and managing the location of nodes in the network.Again, referring back to the example of FIG. 13, master node M1 910 amay take advantage of such a method for locating associated nodes, suchas the locations of ID nodes A-E 920 a-920 e, and update server 100 withthis new location data related to the current location of node M1 andany of the nodes associated with node M1.

Those skilled in the art will appreciate that method 2900 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4, master node M1 910 a in FIG. 13, ormaster node M1 2210 a in FIG. 22A) running one or more parts of mastercontrol and management code 425 (e.g., the location aware/capturemodule). Such code may be stored on a non-transitory computer-readablemedium, such as memory storage 415 on master node 110 a. Thus, whenexecuting code 425, the master node's processing unit 400 may beoperative to perform algorithmic operations or steps from the exemplarymethods disclosed above, including method 2900 and variations of thatmethod.

In another embodiment, a node apparatus is described in a wireless nodenetwork that uses location determination by association as describedwith reference to the steps related to method 2900. As mentioned above,such as node apparatus may be implemented with a master node having anode processing unit, a node volatile memory, a node memory storage, anda first and second communication interface. Each of the memories andcommunication interfaces are coupled to the node processing unit.Further, the node memory storage maintains at least a program codesection, association data, and location data and, at times, shippinginformation. The first communication interface provides a firstcommunication path operatively coupling the node with a plurality ofother nodes in the network, while the second communication interfaceprovides a second communication path operatively and separately couplingthe node with a server in the network.

In this embodiment, the node processing unit is operative to transmitone or more first messages via the first communication interface at afirst anticipated range distance, and identify which of the others nodesthat are associated with the first node received at least one of thefirst messages. In one embodiment, the node processing unit may beoperative to access the association data in the node memory storage whenidentifying which of the nodes associated (e.g., passive, active, orboth types of associations) with the first node received at least one ofthe first messages.

The first anticipated range distance may be an optimal transmissionrange for the first communication interface and, in a more detailedexample, may be adjusted based upon context data (e.g., RF shieldinginherent from the surrounding environment of the node). In yet anotherembodiment, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal transmit from thefirst communication interface may be impeded by an environment of thenode.

The node processing unit is also operative to transmit one or moresecond messages via the first communication interface at a secondanticipate range distance (incrementally smaller than the firstanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the secondmessages but received at least one of the first messages. That locationis between the first anticipate range distance from a known location ofthe node and the second anticipated range distance from the knownlocation of the node. In a further example, the node processing unit maybe operative to store the determined location in the node memory storageas part of the location data.

The node processing unit may also be operative to transmit one or morethird messages via the first communication interface at a thirdanticipated range distance (incrementally smaller range than the secondanticipated range distance) and determine a location of one or more ofthe identified associated nodes that did not receive any of the thirdmessages but received at least one of the second messages, where thelocation is between the second anticipated range distance from the knownlocation of the node and the third anticipated range distance from theknown location of the node.

In another embodiment, the node may be mobile and the node processingunit may be further operative to refine the location of the one or moreof the identified associated nodes that did not receive the secondmessage but received the first message by updating a location of thefirst node. In more detail, the node processing unit may be operative todetermine a current mobile location of the first node (e.g., check withlocation circuitry onboard the node for valid GPS signals and a locationlock based on such signals), and refine the location of the one or moreof the identified associated nodes that did not receive any of thesecond messages but received at least one of the first messages basedupon the current mobile location of the first node. The node processingunit may also be operative to transmit the refined location to theserver over the second communication interface.

Location Determination through ID Node Advertise

While FIG. 13 provides an example of location determination throughmaster node advertising, FIG. 14 focuses on location determinationthrough ID node advertising. In particular, FIG. 14 is a diagramillustrating an exemplary location determination using ID node advertisein accordance with an embodiment of the invention. In the illustratedembodiment shown in FIG. 14, exemplary ID node F 920 f is in anadvertising mode but is without a known location. As with FIG. 13, FIG.14 illustrates the exemplary different RF output power levels from IDnode F 920 f as concentric ranges 1405-1415 about ID node F 920 f. Thus,ID node F 920 f may broadcast at a maximum power P1, related to range1405, but may control the RF output power level and dynamically changethe RF output power level to P2 and broadcast at a smaller range 1410,or to P3 and broadcast to an even smaller range 1415. Master nodes M1-M3910 a-910 c are disposed in various known locations relatively near IDnode F 920 f, which has an unknown location. As such, ID node F 920 fmay take advantage of the ability to adjust an RF characteristic, suchas RF output signal power level, of its own short-range communicationinterface as part of how the system may determine location of ID node Fthrough ID node advertising.

In the illustrated embodiment, an RF output signal power level of IDnode F 920 f may be varied or dynamically adjusted via programmablesettings (such as profile settings or parameters) related to operationsof variable power short range communication interface 375. Additionally,while an actual communication range may vary with the surroundingenvironment, a maximum anticipated communication range of the ID node'stransmitter at each power level is known assuming an optimal operatingenvironment or no substantial RF shielding or interference. Thus, aparticular power level setting for a broadcasting node is inherentlyassociated with a corresponding anticipated range distance.

In an exemplary method of determining a nodes location using ID nodeadvertising, the RF output signal power level may be varied acrossmultiple power levels to improve location through master nodeassociation. In more detail, when the ID node F's variable power shortrange communication interface 375 is set to P1, its maximum output, IDnode F 920 f is seen by each of master nodes M1-3 910 a-910 c. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 at P1power level may have been previously been found to be approximately 30feet. Thus, without any examination of RSSI levels from the individualmaster nodes, the system knows ID Node F is within 30 feet of masternodes M1-M3.

Next, when the ID node F's variable power short range communicationinterface 375 is set to P2, a medium output level in this example, IDnode F 920 f is seen by master nodes M1 910 a and M2 910 b. Theanticipated open air performance or range distance (optimal range, orrange based upon analytics or historic measurements) of the radio in IDnode F's variable power short range communication interface 375 atrunning at P2 power level is approximately 15 feet. Thus, without anyexamination of RSSI levels from the individual nodes, we know masternodes M1 910 a and M2 910 b are within 15 feet of ID node F 920 f inthis example. Furthermore, we know the master node no longer receivingthe broadcasted RF signal from ID node F 920 f (e.g., master node M3 910c) is somewhere within 30 feet of ID node F 920 f, but probably morethan 15 feet away from node F in this example.

And when ID node F's variable power short range communication interface375 is set to P3, its minimum output level in this example, ID node F920 f is seen by only master node M2 910 b. The anticipated open airperformance or range distance (optimal range, or range based uponanalytics or historic measurements) of the radio in ID node F's variablepower short range communication interface 375 at P3 power level isapproximately 5 feet. Thus, without any examination of RSSI levels fromthe master nodes, we know the location of ID node F 920 f is within 5feet of the known location of master node M2 910 b in this example.

The ranging steps with respect to the changed RF characteristics of anadvertising ID node, as discussed in the example above, may then berepeated for any of the identified nodes in order to building a morecomplete picture of the relative location of each node.

Furthermore, the timing between such ranging steps may vary dynamicallydepending upon whether the node is moving. Those skilled in the art willappreciate that when moving, a quicker flow through such ranging stepswill help to provide better accuracy given the movement of nodes. Thus,the time interval between instructing a node to broadcast one or moremessages at a particular power level and then instructing that node tobroadcast one or more messages at a different power level may be desiredto be shorter when the node is moving, which can be determined basedupon context data. For example, the context data may indicate the nodeis within a node package an on a moving conveyor system. As such, thenode is moving relative to fixed master nodes that may be positionedalong the conveyor system. Thus, server may have the first node performthe ranging steps where power is varied in relative quick successioncompared to a situation where the context data indicates the node is notmoving or is substantially stationary.

FIG. 30 is a flow diagram illustrating another exemplary method forlocation determination using one or more associations of nodes in awireless node network in accordance with an embodiment of the invention.Referring to FIG. 30 and how it explains a particular way to locate anode using associations and master node one or more master nodeadvertising techniques, method 3000 begins at step 3005 by instructing afirst of the nodes to broadcast one or more first messages at a firstpower level, the first power level being related to a first anticipatedrange distance. In one example, the first anticipated range distance maybe an optimal range for the first of the nodes (e.g., a transmissionrange that assumes there are no obstructions and a clear signal pathbetween nodes). In another example, the first anticipated range distancemay be an optimal range for the first node adjusted based upon contextdata (e.g., data related to the surrounding RF environment of the firstnode).

At step 3010, the method 3000 identifies which of the nodes associatedwith the first node have known locations at step 3010. For example, thistype of identification may be accomplished by reviewing association datathat indicates which of the nodes are associated with the first node(e.g., via passive association, via active association, or via acombination of both), determining which of the nodes are associated withthe first node based upon the reviewed association data, and identifyingwhich of those associated nodes have known locations.

The method 3000 continues at step 3015 by determining which of theidentified associated nodes received at least one of the first messages.Next, the method 3000 instructs the first node at step 3020 to broadcastone or more second messages at a second power level, where the secondpower level is related to a second anticipated range distance and thesecond power level incrementally smaller than the first power level. Ina further example, the first anticipated range distance and the secondanticipated range distance may be adjusted based upon one or more typesof context data related to how an RF output signal from the first nodemay be impeded.

At step 3025, method 3000 determines which of the identified associatednodes received at least one of the second messages. Method 3000concludes at step 3030 where the method determines a location of thefirst node to be at or between the first anticipated range distance andthe second anticipated range distance from each of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages.

As mentioned above, determining the node's location may be improved whenaccounting for movement. As such, an embodiment of method 3000 mayinstruct the first node to broadcast the one or more second messageswithin a time interval after instructing the first node to broadcast theone or more first messages. The time interval may be predetermined insome implementations, but also may be a dynamically set parameter inother implementations based upon context data related to the first node.In more detail, the time interval may be reduced from a prior value whenthe context data related to the first node indicates the first node ismoving, but may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary.

In another embodiment, method 3000 may further include instructing thefirst node to broadcast one or more third messages at a third powerlevel. Such a third power level is related to a third anticipated rangedistance and incrementally smaller range than the second anticipatedrange distance. Thereafter, the method may determining the location ofthe first node to be at or between the second anticipated range distanceand the third anticipated range distance from each of the identifiedassociated nodes that did not receive any of the third messages butreceived at least one of the second messages.

In another embodiment, method 3000 may comprise refining the location ofthe first node with an updated location of one or more of the identifiedassociated nodes that did not receive at least one of the secondmessages but received at least one of the first messages. For example,if the first node is associated with a mobile master node, the locationof the first node may be refined with an updated location of the mobilemaster node (which may be closer to the first node than previouslydetermined).

In a further embodiment, the first node in the operation of method 3000may not be self-aware of its own location. In another embodiment, thefirst node in the operation of method 3000 may have been previouslyself-aware of the location of the first node but may no longer beself-aware of the location of the first node prior to broadcasting theone or more first messages. In more detail, the first node may no longerbe self-aware of the location of the first node prior to broadcastingthe first message because of a change in the environment surrounding thefirst node. Such a change in the environment may be, for example, whenthe first node has moved inside a structure (e.g., building, vehicle,aircraft, container, etc.) that blocks location signals from beingreceived by the first node.

Those skilled in the art will appreciate that method 3000 as disclosedand explained above in various embodiments may be implemented on a node(e.g., master node 110 a in FIG. 4) running one or more parts of mastercontrol and management code 425 (e.g., the location aware/capturemodule) to control operations of an ID node (such as ID node F in FIG.14) as part of location determination via ID node advertising. Such codemay be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a. Thus, when executing code 425,the master node's processing unit 400 may be operative to performalgorithmic operations or steps from the exemplary methods disclosedabove, including method 3000 and variations of that method.

From an apparatus perspective, an exemplary node apparatus in a wirelessnode network that uses location determination by association maycomprises a node processing unit, node memory coupled to and used by thenode processing unit (e.g., a node volatile memory and a node memorystorage). The node memory storage maintains at least a program codesection, association data, and location data. The node apparatus furtherincludes a first communication interface that provides a firstcommunication path coupled to the node processing unit and operativelycoupling the node with a plurality of other nodes in the network. Forexample, the master node 110 illustrated in FIG. 4 includes such typesof operational structure.

The node processing unit (e.g., processing unit 400 of master node 110a), when executing at least the program code section resident in thenode volatile memory, is operative to perform specific functions orsteps. In particular, the node processing unit is operative tocommunicate an instruction to a first of the other nodes (e.g., an IDnode or master node temporarily operating as an ID node) via the firstcommunication interface to cause the first other node to broadcast oneor more first messages at a first power level, where the first powerlevel is related to a first anticipated range distance.

The first anticipated range distance may be an optimal range for thefirst of the nodes and, in more detail, an optimal range for the firstof the nodes adjusted based upon context data. In even more detail, thefirst anticipated range distance and the second anticipated rangedistance may be adjusted based upon one or more types of context datarelated to how an RF output signal broadcast from the first node may beimpeded.

The node processing unit is also operative to identify which of thenodes associated with the first node have known locations. To do this,the node processing unit may access and review association data storedon the node memory storage (e.g., data indicating what nodes arepassively or actively associated with the first other node), maydetermine which of the remaining other nodes are associated with thefirst other node based upon the reviewed association data, and mayidentify which of the remaining other nodes determined to be associatedwith the first other node have known locations.

The node processing unit is also operative to determine which of theidentified associated nodes received at least one of the first messages,and to communicate another instruction via the first communicationinterface to the first node to cause the first node to broadcast one ormore second messages at a second power level, where the second powerlevel being is to a second anticipated range distance and incrementallysmaller than the first power level.

Finally, the node processing unit is operative to determine which of theidentified associated nodes received at least one of the secondmessages, and then determine a location of the first node to be at orbetween the first anticipated range distance and the second anticipatedrange distance from each of the identified associated nodes that did notreceive at least one of the second messages but received at least one ofthe first messages.

In a further embodiment, the node processing unit may be operative tocommunicate a third instruction via the first communication interface tothe first node to cause the first node to broadcast one or more thirdmessages at a third power level. The third power level is related to athird anticipated range distance and incrementally smaller range thanthe second anticipated range distance. Additionally, the node processingunit may then be operative to determine the location of the first nodeto be at or between the second anticipated range distance and the thirdanticipated range distance from each of the identified associated nodesthat did not receive any of the third messages but received at least oneof the second messages.

In still another embodiment, the node processing unit is able to accountfor movement of the first node with a time interval between instructionssent to the first node. In particular, the node processing unit may befurther operative to communicate another instruction via the firstcommunication interface to the first node to broadcast the secondmessages within a time interval after instructing the first node tobroadcast the first messages. In a more detailed example, the timeinterval may be dynamically set based upon context data related to thefirst node. In even more detail, the time interval may beprogrammatically reduced from a prior value when the context datarelated to the first node indicates the first node is moving (e.g., thefirst node is on a moving conveyor system) and/or the time value of theinterval may be increased from a prior value when the context datarelated to the first node indicates the first node is substantiallystationary (e.g., the node is within a node package recently placed in astorage area).

The node processing unit, in a further embodiment, may be operative torefine the location of the first other node with an updated location ofone or more of the identified associated nodes that did not receive atleast one of the second messages but received at least one of the firstmessages, and cause a second communication interface (e.g., medium/longrange communication interface 485 coupled to processing unit 400) totransmit the refined location to the server.

From a server perspective, FIG. 31 is a flow diagram (similar to FIG.30) illustrating yet another exemplary method for location determinationusing one or more associations of nodes in a wireless node network inaccordance with an embodiment of the invention. Those skilled in the artwill appreciate that while a server may operate to implement the stepsas laid out in method 3000 and discussed above, FIG. 31 provides moredetails as to how a server processing unit (such as processing unit 500running server code 525) may implement such a method at that level ofthe network via method 3100. In this more detailed embodiment, theserver is communicating directly with a master node (e.g., a first node)to direct and control how the master node interacts with and causesoperations to be undertaken on the ID node (e.g., a second node). Thus,step 3105 is similar to step 3005 but more precisely calls forcommunicating with a first node via a communication interface to cause asecond node in the network to broadcast one or more first messages at afirst power level at the request of the first node, where the firstpower level is related to and corresponds with a first anticipated rangedistance. Likewise, step 3120 is similar to step 3020 but more preciselycalls for communicating with the first node via the communicationinterface to cause the second node to broadcast one or more secondmessages at a second power level at the request of the first node, thesecond power level being related to a second anticipated range distanceand incrementally smaller than the first power level. The other steps ofmethod 3100 are similar to those illustrated and explained aboverelative to method 3000, and that the similar principles will apply tomethod 3100.

Those skilled in the art will appreciate that method 3100 as disclosedand explained above in various embodiments may be implemented on aserver (e.g., server 100 in FIG. 5) running one or more parts of servercontrol and management code 525 to direct a master node to controloperations of an ID node (such as ID node F in FIG. 14) as part oflocation determination via ID node advertising. Such code may be storedon a non-transitory computer-readable medium, such as memory storage 515on server 100. Thus, when executing code 525, the server's processingunit 500 may be operative to perform algorithmic operations or stepsfrom the exemplary methods disclosed above, including method 3100 andvariations of that method.

And similar to the node apparatus described above, one embodimentincludes an exemplary server apparatus in a wireless node network thatuses location determination by association. The exemplary serverapparatus generally comprises a server processing unit, server memorycoupled to and used by the server processing unit (e.g., a servervolatile memory and a server memory storage). The server memory storagemaintains at least a program code section, association data, andlocation data. The server apparatus further includes a communicationinterface coupled to the server processing unit and that provides accessto a communication path operatively coupling the server with at least afirst node in the network.

The exemplary server processing unit, when executing at least theprogram code section resident in the server volatile memory, isoperative to perform specific functions or steps. In particular, theserver processing unit is operative to communicate with the first nodevia the communication interface to cause a second node in the network tobroadcast one or more first messages at a first power level at therequest of the first node, where the first power level is related to afirst anticipated range distance; identify which of the remaining nodesin the network associated with the second node have known locations;determine which of the identified associated nodes received at least oneof the first messages; communicate with the first node via thecommunication interface to cause the second node to broadcast one ormore second messages at a second power level at the request of the firstnode, where the second power level is related to a second anticipatedrange distance and incrementally smaller than the first power level;determine which of the identified associated nodes received at least oneof the second messages; and determine a location of the second node tobe at or between the first anticipated range distance and the secondanticipated range distance from each of the identified associated nodesthat did not receive any of the second messages but received at leastone of the first messages. And in a further embodiment, the serverapparatus' processing unit may be further operative to store thedetermined location in the server memory storage as part of the locationdata.

In another embodiment, the server apparatus' processing unit may beoperative to communicate with the first node via the communicationinterface to cause the second node to broadcast the one or more secondmessages within a time interval after communicating with the first nodeto cause the second node to broadcast the one or more first messages. Aspreviously mentioned, this type of time interval may dynamically setbased upon context data related to the second node. Context data mayalso be used as set forth above with respect to the node apparatus butapplied here to the second node—such was where the first anticipatedrange distance is the optimal range for the second node adjusted basedupon context data.

Master Node Location Determination through Advertise

In another embodiment, a master node may no longer know its location.For example, such a situation may occur when a master node determinesit's current location via GPS location circuitry 475, but the masternode finds itself without access to an adequate number of GPS signals(e.g., it cannot determine a location due to the lack of a sufficientnumber of GPS signals from diverse GPS satellites). Such a situation mayhappen when the master node moves indoors is proximate to a structurethat interferes with the location signals.

In an exemplary embodiment where a master node attempts to determine itsown location via advertising techniques, the master node may detect aloss of location confidence (e.g., upon a loss of detected GPS signals;upon detecting a separate signal to processing unit 400 indicating themaster node's location is unknown; when processing unit 400 sensesmovement (e.g., via accelerometers (not shown) or the like) but cannotconfirm that the location circuitry 475 is providing updated locationinformation for the node, etc.). In other words, the master node becomesaware that it no longer has a known location.

Next, the master node responds by beginning to broadcast one or moreadvertising messages in a similar way as ID node F 920 f is described asdoing with respect to FIG. 14. This is done so that the master nodehaving an unknown location can advantageously leverage off the knownlocations of nearby other nodes. As such, an embodiment may allow a typeof leveraged chaining effect whereby known locations of particular typesof nodes may be used to extend location information to other nodes thatdo not know their locations (e.g., ID nodes) or nodes that have detecteda loss of location confidence (e.g., master nodes). Thus, such anembodiment may be used to determine an indoor location of a master node(including equipment equipped with master node functionality) in caseswhere signals for the conventional onboard location circuitry 475 arenot available.

Referring back to the exemplary method 3000 and FIG. 30, method 3000 maybe such that the first node is not self-aware of the location of thefirst node. This may happen when the first node (e.g., an ID node) isactually a master node that was previously self-aware of its ownlocation (e.g., via received GPS signals) but is no longer self-aware ofits location (e.g., when the GPS signals can no longer be received),which has the master node changing operation to operate as an ID nodeprior to broadcasting the first message. In other words, the master nodemay no longer be self-aware of its location and begin operating as an IDnode for purposes of location determination prior to broadcasting thefirst message because of a change in the environment surrounding themaster node, such as when the master node has moved inside a structurethat blocks location signals from being received by the master node.Thus, an embodiment may advantageously allow a node to adaptively alteroperations when moving from a clear outdoor environment to an indoorenvironment. And a server may interact with such a master node whilethat master node is operating, for location purposes, as an ID node,temporarily.

Location with Improved RSSI Measurements

In another embodiment, a signal strength measurement between two or morenodes may be used to determine the proximity of the nodes by using oneor more improvements to conventional RSSI measurements. In conventionalRSSI measurements, such as with Bluetooth 4.0, those skilled in the artwill appreciate that adaptive frequency hopping as part of spreadspectrum techniques may cause undesirably cause the signal strength tofluctuate. In other words, the advantage of using frequency hopping andspread spectrum for security and avoidance of interference may have anegative impact on using such signals for stable proximity-basedlocation determinations. Thus, it may be desired to emphasize stabilityof a signal and limits to fluctuation for purposes of locationdetermination.

In one embodiment, a type of improvement for RSSI measurements mayinclude reducing the number of channels and/or a corresponding frequencyrange in use during advertising from nodes. For example, a node may haveprocessing unit 300/400 adaptively control variable power short rangecommunication interface 375/480 to reduce the number of channels and/orthe frequency range used during node advertising. Such a dynamic changemay be implemented, in some embodiments, by altering the content of aparticular type of profile data 330/430, such as an RF profile data thateffectively defines RF characteristics of a node (e.g., frequency, powerlevel, duty cycle, channel numbers, channel spacing, alternativefluctuation modes, etc.). In one further embodiment, a first fluctuationmode may be defined that provides a default or more standardcommunication protocol, such as the conventional frequency hopping,spread spectrum, and channel allocations for Bluetooth® communications.Other alternative modes (one or more) may be defined that alter one ormore RF characteristics to provide increasingly more stable and lessfluctuations of the RF output signal from a node. Thus, a node may bedynamically placed into one or more modes regarding such RFcharacteristics that increasingly emphasize stability of the node's RFoutput signal and limits fluctuation for purposes of enhanced locationdetermination using RSSI measurements.

In another embodiment, a type of improvement for RSSI measurements mayinclude ensuring visibility to and advantageously managing automaticgain control (AGC) circuitry (not shown) that may cause the RF outputsignal to vary for a node. For example, a node may include a type of AGCcircuitry as part of variable power short range communication interface375/480. This type of AGC circuitry may allow node processing unit300/400 or other logic circuitry that is part of variable power shortrange communication interface 375/480 to limit fluctuations undercertain conditions (e.g., when attempting to use RSSI locationdetermination techniques). In this example, different AGC circuitrysettings may be defined in exemplary RF profile data that effectivelydefines RF characteristics of a node (e.g., frequency, power level, dutycycle, channel numbers, channel spacing, alternative fluctuation modes,etc.). This is yet another example of how a node may be dynamicallyplaced into one or more modes regarding such RF characteristics(including AGC circuitry settings) that increasingly emphasize stabilityof the node's RF output signal and limits fluctuation for purposes ofenhanced location determination using RSSI measurements.

Location with Adjustments for Environmental Factors in RF Signal Quality

In general, those skilled in the art will appreciate that environmentalfactors may cause a communication signal, such as an RF signal, tofluctuate or be transmitted and received in a manner that undesirablyvaries depending upon a signal path environment. Passive physicalinterference factors (e.g., forms of electronic signal shielding) may besubstantially close and cause drops in signal strength across the outputranges of the nodes. Additionally, active radio interference factors mayvary across the RF output ranges of the nodes depending upon otheractive devices in the reception vicinity. Thus, the proximateenvironment of a node may have a multitude of adverse factors thatimpact communications and, as a result, the ability to locate the node.

In one embodiment, making location determinations may be enhanced by adata analytics type of approach that may adjust and account fordifferent RF environmental factors for a similar type of node in asimilar type of situation. For example, the quality of the RF outputsignal of a particular type of node and the corresponding physical rangeof that signal to a receiver of known sensitivity may be determined fora given environment. In this example, the system defines a maximum rangeof that signal based on a predetermined condition, such as open-airconnectivity. This may assume an environment with no signal degradationdue to interference or physical shielding. However, both interferenceand physical shielding may diminish the range of the RF output signal ofa node. In a dynamically adaptive and learning manner, the system maycollect information on how a particular type of node may operate in aparticular environment under certain settings (e.g., reported signalstrengths and corresponding settings for RF output signal power levels).This analysis of a similar environment may be repeated. In other words,through such data analytics of an anticipated environment to be faced bya similar node, signal loss information can be generated and applied asa type of context data (i.e., RF data) for a node in a similarenvironment to refine location determination. Thus, an exemplaryembodiment may refine location determinations with adaptive signal losscharacteristics based on a contextual appreciation of an anticipatedenvironment (e.g., physical shielding such as packaging, packagecontents, proximate package, proximate package contents, and physicalinfrastructure causing signal variance) without requiring a calibrationphase.

And advantageously combining those data points with 3^(rd) party datadescribing the physical environment, in which the node was located in atthat time, may refine location even further. Such information may beused as RF data (a type of context data) in future efforts to manage andlocate a similar type of node anticipated to be in a similarenvironment.

In more detail, in an embodiment that refines a location determinationbased upon context and data analytics to adjust for known RFimpediments, the maximum physical range of a node's RF output signalrelative to a receiver of known RF sensitivity is determined. In oneexample, this first range value may be referred to as a theoretical ornominal open-air range of a similar type transmitter-receiver node pairin a similar environment but with substantially no physical shielding orsignal interference negatively impacting the signal range. A secondrange value, which may be considered an actual RF range value, may bethe observed range of the signal in a similar environment but wherethere are contextual factors reducing the communication range, includingphysical shielding due to factors like packaging, package contents,proximate package, proximate package contents, physical infrastructure,interference from other radio sources, or shipper specific informationsuch as vehicle or facility layout information. Through access to priordata analysis of the differing range values and with knowledge of theoperational environment of the transmitting node was in (e.g., a similarenvironment to the proximate environment of the node), a refinedlocation may be determined using an approximation of an actual RF outputrange that intelligently adjusts what may be anticipated to be the RFenvironment of the node. In other words, by knowing the appropriatecontextual environment related to a node (such as signal degradationinformation on how a similar node operates in a similar environment), animproved location determination may be made to make intelligent yetefficient adjustments (such as communication distance adjustments) thatprovide a refined location of the node.

In one example, such as the example shown in FIG. 2, master node 110 bis outside of a container (such as a Uniform Load Device (ULD) container210 known to be used for transporting groups of items on aircraft) thathas an ID node inside the container. A first or theoretical range valuebetween master node 110 b and ID node 120 b may be determined to be 10feet at a specific RF output power level when the package (and relatedID node) may be known to be less than 10 feet away from the scanningnode (e.g., master node 110 b). A second range value at similardistances with similar types of nodes, but with incident RF signal lossas a result of communicating through the wall of the container 210, maybe between 4 and 5 feet. If context data, such as 3^(rd) partyinformation or scan data, indicates the transmitting node is within theULD container 210, the system would expect the transmission range to belimited according to the data analytics associated with this known RFimpediment (e.g., characteristics for transmitting through ULD container210), thus reducing the possible scanning nodes that may see thebroadcasting node within the ULD container, or require the transmittingnode to increase its RF output power to be heard.

FIG. 32 is a flow diagram illustrating an exemplary method for locationdetermination of a first node in a wireless node network based oncontext data in accordance with an embodiment of the invention.Referring now to FIG. 32, method 3200 begins at step 3205 with a networkdevice (such as a master node or server) accessing a first type of thecontext data related to a proximate environment of the first node.

The first type of context data comprises signal degradation informationon how a second node would operate in a similar environment to theproximate environment of the first node when the second node is asimilar type as the first node. Thus, rather than calibrating with anactual measurement relative to the current proximate environment of thefirst node, the signal degradation information provides compensationinformation on what may be generally anticipated in a more generalproximate environment based on how a similar type of node may operate ina similar environment. As the similar environment of the similar node isgenerally an approximation for what is anticipated to be the proximateenvironment of the first node, this advantageously avoids the need foran actual calibration of the proximate environment. In one embodiment,the signal degradation information may be based upon a difference in howthe second node communicates when exposed to an adverse communicationenvironment (such as a similar environment to the proximate environmentof the first node) compared to how the second node would communicateswhen exposed to a nominal communication environment (such as anenvironment that is unencumbered by shielding and interference factors).Those skilled in the art will appreciate that a nominal communicationenvironment need not be perfectly clear of all influences that shield orinterfere with communications.

The types and aspects of signal degradation information may varydepending on a wide variety of factors. In one embodiment, the signaldegradation information may be related to at least one of shielding andinterference. Thus, signal degradation information may include bothpassive and active factors that impact the communication environment.

In another embodiment, the signal degradation environment may be basedupon a degraded operation of the second node when the similarenvironment is an adverse communication environment. In more detail, thesignal degradation information may be based upon a difference in how thesecond node communicates when exposed to the adverse communicationenvironment compared to how the second node communicates when exposed toa substantially normal communication environment, such as an open airenvironment.

In still another embodiment, signal degradation information may relateto at least shipment data for one or more items being shipped (e.g.,currently shipped or shipped in the past) and located in the proximateenvironment of the first node. For instance, a package near the firstnode may include metallic materials that may impede or block RF signalsand the signal degradation information may relate to such informationabout close packages being shipped near the first node. In anotherexample, the signal degradation information may relate to at leastlayout data for one or more physical structures in the proximateenvironment of the first node. In more detail, the layout data may befor one or more physical structures (e.g., walls, machinery, enclosures,and conveyances) in the proximate environment of the node near apredicted path for the first node. In yet another example, the signaldegradation information relates to at least historic data on one or moreanalyzed prior operations of the second node.

At step 3210, the network device, such as a master node or server, mayadjust an anticipated communication distance related to the first nodebased upon on the first type of the context data. In one example, theanticipated communication distance may be a theoretical broadcastdistance based upon parameters of the device's radio. Such ananticipated communication distance is known as it is an estimate of theradio's range. In one example, the adjusted communication distancecomprises an anticipated reduced range distance for a transmission fromthe first node. In another example, the adjusted communication distancecomprises an anticipated reduced receiver sensitivity distance for thefirst node.

In yet another example, adjusting the communication distance may beaccomplished by adaptively adjusting, by the network device, thecommunication distance based upon the signal degradation information anda second type of the context data. In other words, the communicationdistance may be adjusted based upon signal degradation informationconsidered along with other types of context data, such as how the firstnode is being moved (such as an anticipated movement of the first nodealong a predicted transit path for the first node) or a density of othernodes near the first node.

At step 3215, the network device determines the location of the firstnode based upon the adjusted communication distance. In a furtherembodiment, the method may also update the adjusted communicationdistance by the network device based upon movement of the first node,and may refine the location of the first node with an updated adjustedcommunication distance. This may happen with the first node is a mobilemaster node capable of self-determining its own location.

Those skilled in the art will appreciate that method 3200 as disclosedand explained above in various embodiments may be implemented on anetwork device (e.g., exemplary master node 110 a in FIG. 4 or server100 in FIG. 5) running one or more parts of their respective control andmanagement code to perform steps of method 3200 as described above. Suchcode may be stored on a non-transitory computer-readable medium, such asmemory storage 415 on master node 110 a or memory storage 515 on server100. Thus, when executing such code, the respective network device'sprocessing unit may be operative to perform algorithmic operations orsteps from the exemplary methods disclosed above, including method 3200and variations of that method.

In more detail, an exemplary network device apparatus for determining alocation of a first node in a wireless node network based on contextdata, the exemplary network device may include a processing unit, avolatile memory coupled to the processing unit, and a memory storagecoupled to the processing unit. The exemplary network device furtherincludes a communication interface coupled to the processing unit andthat provides a communication path operatively coupling the networkdevice with the first node in the network.

The memory storage for the device maintains at least a program codesection and context data having at least signal degradation information.Such signal degradation information, as a type of context data, isinformation on how a second node would operate in a similar environmentto a proximate environment of the first node when the second node is asimilar type as the first node. Examples of signal degradationinformation may include those discussed above relative to step 3205 ofmethod 3200.

When executing at least the program code section when resident in thevolatile memory, the processing unit of the network device is operativeto perform the steps noted and described above with respect to method3200. In more detail, the processing unit is operative to at leastconnect with the memory storage to access the signal degradationinformation, adjust a communication distance (if needed) related to thefirst node based upon on the signal degradation information, determinethe location of the first node based upon the adjusted communicationdistance, and store the determined location of the first node aslocation data on the memory storage.

Adjusting the communication distance by the processing unit may beaccomplished as described above with regard to step 3210 of method 3200.And as mentioned above, the processing unit may be further operative toadaptively adjust the communication distance where other types ofcontext data are also considered, such as movement and anticipated nodemovement as detailed out above.

In a further embodiment, the network device may be a mobile master nodethat includes location circuitry (such as GPS circuitry 475 of exemplarymaster node 110 a shown in FIG. 4). In this embodiment, the processingof the network device may be further operative to determine a locationof the network device based upon an output signal from the locationcircuitry received by the processing unit, and determine the location ofthe first node based upon the adjusted communication distance and thelocation of the network device. As such, the first type of the contextdata related to the proximate environment of the first node is basedupon the determined location of the first node.

Those skilled in the art will also appreciate that in some operationalenvironments, the signal degradation information may not require anyadjustment to the communication distance in an embodiment. However, inother environments (e.g., adverse RF environments), the signaldegradation information may provide a basis for adjusting thecommunication distance in the embodiment, even if not performed everytime. Thus, an adjustment to the communication distance may not beneeded in all proximate environments of the first node but may beperformed, if needed, based on the proximate environment of the firstnode. It is the ability of an embodiment to adjust this communicationdistance when needed and if needed that advantageously allows forlocating the first node with more accuracy.

Location through Triangulation

In some embodiments, various methods for determining a node's locationmay rely upon, at least in part, triangulation techniques. In otherwords, as the wireless node network collects data onreceiver-transmitter pairs, other methods for determining location ofthe individual nodes that utilize triangulation, at least in part, maybecome possible. FIG. 15 is a diagram illustrating an exemplary locationdetermination through triangulation within a wireless node network inaccordance with an embodiment of the invention. Referring now to theillustrated embodiment of FIG. 15, three exemplary master nodes M1-M3910 a-910 c are shown with each master node having a known location.Exemplary ID nodes A-E 920 a-920 e are also shown where they are atleast in communication range of one or more of exemplary master nodesMA-M3 910 a-910 c.

In this illustrated example, the master nodes M1-M3 may detect andcollect advertising messages from ID nodes A-E at varying and knownpower levels. The captured information is forwarded by the master nodesM1-M3 to the backend server 100, where location determinations may bemade. For example, factors like RSSI and visibility of each node at eachpower level may be used to determine, with a higher degree of accuracy,the location of nodes where sufficient information is available.

For an exemplary system to triangulate a node, three nodes with knownlocations must have seen the broadcasting node. In this example, twoadvertising ID nodes, A 920 a and B 920 b, were seen by the three nodeshaving known locations (master nodes M1-M3 910 a-910 c). Based upon thecaptured information, the locations of ID node A 920 a and ID node B 920b are calculated.

Chaining Triangulation

In another embodiment, a node with an inferred location may be used withtriangulation techniques to determine a location of another node in awireless node network. FIG. 16 is a diagram illustrating an exemplarylocation determination through chaining triangulation in accordance withan embodiment of the invention. The locations of ID nodes A 920 a and B920 c have been determined by triangulating across master nodes M1-M3,as illustrated in the exemplary embodiment shown in FIG. 15. However, asillustrated in FIG. 16, the location of ID node C 920 c may also bedetermined according to an embodiment.

For example, an exemplary method of determining a node's locationthrough chaining triangulation begins with determining the calculatedlocation of ID node B 920 b (as explained with reference to FIG. 15).Next, a node closer to ID node B 920 b may be used to get the missingthird signal point needed for triangulation. This may be accomplished byplacing ID node B 920 b in a query (scan) mode such that it listens fora message from ID node C 902 c. ID node C is instructed to advertise,thus providing a signal that may be captured by ID node B. Aftercapturing the signal profile of C, ID node B may communicate or sharethe captured information and forward it along to the backend server 100through either of the master nodes M1 or M2. The resulting locationdetermination of ID node C 920 c may have a higher level of positionerror due to it being partially based on a calculated reference (e.g.,the location of ID node B), but the leveraged location determination ofID node C 920 c may be sufficiently accurate (or be an actionablelocation) that useful information may be gleaned about ID node C 920 c.For example, a leveraged or chained location determination of ID node Cmay indicate, with the help of context data, that nodes M1, M2, and IDnode B are all close enough to ID node C that ID node C is determined tobe within the same container nodes M1, M2, and ID node B.

Location through Proximity to Triangulation (LP2T)

In an embodiment where chaining triangulation may determine locationthrough proximity to triangulation (LP2T), a starting point may bedetermining the relative location of an ID node to a master node basedon the proximity method, as explained above. However, when the relativelocation of the ID node has been determined, a more accurate or refinedlocation of the ID node may be determined based upon the location of allmaster nodes that can capture the RF output signal broadcast from the IDnode, and then triangulating based on observed signal strength of the IDnode. In this example, the proximity-based location is used as an inputin the triangulation calculation to estimate likely signal deteriorationhistorically observed between a node at the proximity-determinedlocation and scanning master nodes. In a further embodiment, by takinginto account historic data on patterns of signal deterioration, a moreaccurate triangulation may be possible, leading to a more accuratelocation determination.

FIG. 33 is a flow diagram illustrating an exemplary method fordetermining a node location using chaining triangulation for one of aplurality of nodes in a wireless node network having a server inaccordance with an embodiment of the invention. Such an exemplary nodelocation need not be precise or exacting, but can be sufficientlyaccurate without absolutes.

Referring now to FIG. 33, method 3300 begins at step 3305 with theserver receiving a location of a first of the nodes from the first node.Next, at step 3310, the server receives a location of a second of thenodes from the second node. For example, with reference to the exampleshown in FIG. 16, master nodes M1 910 a and M2 910 b may transmit theirrespective location coordinates from their respective onboard locationcircuitry to the server so that the server has the current locations ofthese two master nodes.

At step 3315, the server infers a location of a third of the nodes. Forinstance, in the example illustrated in FIG. 16, the server may inferthe location of ID node B 920 b. In one embodiment, inferring maycomprise having the server determine a proximate-based location of thethird node relative to another of the nodes having a known location,such that the proximate-based location operates as the inferred locationof the third node.

In another embodiment, inferring the location of the third node maycomprise having the server determine a relative location of the thirdnode to the first node (as the node having a known location) or to thesecond node (as another node having a known location). Method 3300 mayalso, in another embodiment, include having the server adjust theinferred location of the third node to determine a refined location ofthe third node based upon third node context data related to theinferred location of the third node

At step 3320, method 3300 concludes with the server triangulating thelocation of the one node based upon determined distances to each of thefirst and second nodes, and a determined distance of the one node to theinferred location of the third nodes.

In a more detailed embodiment, method 3300 may triangulate the locationof the one node by accessing first node context data related to acontextual environment near the first node and second node context datarelated a contextual environment near the second node. Such contextualenvironments may include an environment of being on a conveyor system,or within a particular facility, or next to materials that may degradeor shield signals being received by the one node. Next, the moredetailed triangulating may have the server adjust the determineddistance of the one node to the location of the first node based uponthe first node context data to provide a refined distance of the onenode to the location of the of the first node. Then, the server maytriangulate the location of the one node based upon the adjusteddetermined distance of the one node to the location of the first node,the adjusted determined distance of the one node to the location ofsecond node, and a determined distance of the one node to the refinedlocation of the third node.

In a further embodiment, method 3300 may also have the servertransmitting an instruction so as to cause the server to transmit aninstruction to cause the one node to broadcast a plurality ofadvertising signals over a period of time. In such an embodiment, thedetermined distance of the one node to the location of the first nodemay be based upon captured signals from the one node by the first nodeover the period of time and reported to the server by the first node. Inanother embodiment, the determined distance of the one node to thelocation of the second node may be based upon captured signals from theone node by the second node and reported to the server by the secondnode.

In still another embodiment, the server may transmit an instruction tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. In another embodiment, the determined distanceof the one node to the location of the second node may be based uponcaptured signals from the one node by the second node and reported tothe server by the second node.

In yet another embodiment, method 3300 may also have the servertransmitting the location information out to a requesting entity (e.g.,another node, a user access device, etc.) upon receipt of a request fora location of the one node from that entity.

Those skilled in the art will appreciate that method 3300 as disclosedand explained above in various embodiments may be implemented on aserver (such as exemplary server 100 as illustrated in FIG. 5) runningone or more parts of a control and management code (such as an code 525)to implement any of the above described functionality. Such code may bestored on a non-transitory computer-readable medium (such as memorystorage 515 in an exemplary server). Thus, when executing such code, aprocessing unit of the server (such as unit 500) may be operative toperform algorithmic operations or steps from the exemplary methodsdisclosed above, including method 3300 and variations of that method.

A server apparatus is also described in an embodiment for determining alocation using chaining triangulation for one of a plurality of nodes ina wireless node network. The server apparatus generally comprises aserver processing unit, a server volatile memory, a server memorystorage, and a communication interface. The server volatile memory,server memory storage, and communication interface are each configuredin the apparatus as coupled to the server processing unit. The servermemory storage maintains at least a program code section and locationdata related to nodes in the network. In some embodiments, the servermemory storage may also maintain context data, such as first nodecontext data and second node context data. The communication interfaceprovides a communication path operatively coupling the server with nodesin the network, such as a first and second node.

The server processing unit, when executing at least the program codesection resident in the server volatile memory, is operative to performvarious functions, such as the functions described in the steps aboverelated to method 3300. In particular, the server processing unit isoperative to receive a request over the communication interface for thelocation of the one node. Based on the request, the server processingunit is then operative to receive the respective locations of the firstand second nodes, and store the locations as part of the location datakept on the server memory storage. The server processing unit is furtheroperative to infer a location of a third of the nodes, and store theinferred location of the third node as part of the location data kept onthe server memory storage. The server processing unit then is operativeto triangulate the location of the one node based upon a determineddistance of the one node to the location of the first node, a determineddistance of the one node to the location of second node, and adetermined distance of the one node to the inferred location of thethird node. And finally, the server processing unit is operative totransmit the location information to the requesting entity over thecommunication interface in response to the request.

In one embodiment, the server processing unit may be further operativeto infer the location of the third of the nodes by being operative todetermine a proximate-based location of the third node relative toanother of the nodes having a known location, where the proximate-basedlocation operates as the inferred location of the third node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals overa period of time. In this embodiment, the determined distance of the onenode to the location of the first node may be based upon capturedsignals from the one node by the first node over the period of time andreported to the server by the first node. Alternatively, the determineddistance of the one node to the location of the second node may be basedupon captured signals from the one node by the second node and reportedto the server by the second node.

In another embodiment, the server processing unit may be furtheroperative to transmit an instruction over the communication interface tocause the one node to broadcast a plurality of advertising signals atdifferent power levels. In such an embodiment, the determined distanceof the one node to the location of the first node may be based uponcaptured signals from the one node by the first node and reported to theserver by the first node. Alternatively, the determined distance of theone node to the location of the second node may be based upon capturedsignals from the one node by the second node and reported to the serverby the second node.

In yet another embodiment, the server processing unit may be furtheroperative to infer the location of the third node by being operative todetermine a relative location of the third node to the first node or,alternatively, to the second node.

In still another embodiment, context data may be relied upon to refinelocations. More specifically, the server processing unit may be furtheroperative to adjust the inferred location of the third node to determinea refined location of the third node based upon third node context datarelated to the inferred location of the third node.

In a more detailed embodiment, the server memory storage may furthermaintains context data, and the server processing unit may be furtheroperative to triangulate by being operative to access first node contextdata as part of the context data maintained on the server memorystorage, where the first node context data is related to a contextualenvironment near the first node. Likewise, the server processing unitmay be further operative to access second node context data as part ofthe context data maintained on the server memory storage, where thesecond node context data is related a contextual environment near thesecond node. The server processing unit may then be operative to adjustthe determined distance of the one node to the location of the firstnode based upon the first node context data to provide a refineddistance of the one node to the location of the of the first node. Assuch, the server processing unit may be operative to triangulate thelocation of the one node based upon the adjusted determined distance ofthe one node to the location of the first node, the adjusted determineddistance of the one node to the location of second node, and adetermined distance of the one node to the refined location of the thirdnode.

Combined Methods for Determining Node Location

In light of the examples explained above for locating a node, oneskilled in the art will appreciate that a further embodiment expresslycontemplates using more than one of the above-described locationdetermination techniques when determining a refined location of a nodein a wireless node network. For example, such combination embodimentsmay apply an ordered or prioritized approach whereby a first locationtechnique is applied to generate first location information regardingthe location of a node in the wireless network. Thereafter, a secondlocation technique may be selected from a hierarchy or prioritized setof techniques (some of which may work better in certain circumstancesand be chosen or dynamically prioritized based upon the contextualenvironment), and applied to generate second location informationregarding the location of the node or refining the location of the node.Other embodiments may apply additional location techniques to generatefurther refined location information.

In an embodiment, the information in the exemplary hierarchy generallyidentifies which technique may be preferred to be used initially as wellas a ranked grouping or listing of when to apply other locationtechniques. Such information in the exemplary hierarchy may be fixed(based upon successful historic data and experience) or be dynamicallyaltered over time as nodes may move relative to each other and, forexample, based upon context data that provides more information relativeto the a current or anticipated contextual environment.

Applying Node Location Determination in a Vehicular Environment

The various exemplary methods and techniques described above fordetermining the location of a node provide an advantageous way to locatea node. However, further embodiments may advantageously apply suchmethods and techniques in a vehicular environment when dealing withlogistics operations where a node is to be located in a vehicle, movedwithin a vehicle, or removed for delivery from a vehicle.

Essentially, embodiments may use a package enabled with a node(generally referred to as a node package or node-enabled package) toship one or more items and such a node package may be advantageouslyplaced, located, moved, or removed for delivery in avehicle/transportation/shipping/logistics environment. As explainedthroughout this description, a node package is generally a package to beshipped that is related to a particular node. The node and the relatedpackage travel together as part of the shipping process. In a generalembodiment, the node may simply be within the package. In anotherembodiment, the node may be attached to the package (e.g., adhered to aninterior portion of the package, fixed to a part of the package whereone or more status indicators of the node may be visible through thepackage, etc.). In another embodiment, the node of the node package maybe part of the package or the packaging materials used to comprise anexterior, interior, or separating/cushioning material within the nodepackage. In more detail, the node may be integrated as part of thepackage or packaging materials (e.g., integrated as part of a pallet, aULD container, a corrugated fiberboard box, and the like). In stillanother detailed embodiment, the node of the node package may be fullyor partially embedded within the package or packaging materials used tohelp form a general container, which maintains an item to be shippedalong with the node.

FIG. 20 is a diagram illustrating exemplary node packages located in anexemplary vehicle environment in accordance with an embodiment of theinvention. Referring now to FIG. 20, exemplary vehicle 9300 isillustrated as an example of a general mobile logistics transport orconveyance carrying packages being shipped. Those skilled in the artwill appreciate that vehicle 9300 may be implemented as various types oflogistics conveyances (e.g., automobile, delivery van, autonomousvehicle, truck, trailer, train, aircraft, marine vessel (ship), etc.).Within exemplary vehicle 9300, packages may be placed, stored, andorganized within different storage devices or units, such as storageunit A 9305 or storage unit B 9310. In general, a storage device or unithelps to maintain one or more packages in a configuration that helps toassure save shipment, minimize damage to the packages, and provide a wayto organize what is being stored. Different embodiments of a storageunit may store a single package or may storage a wide variety ofdifferent types of packages that use different types of packagingmaterials (e.g., corrugated fiberboard boxes, wooden and non-woodenpallets, containers, etc.) and in large numbers.

Vehicle 9300 includes a vehicle master node 9315—an exemplaryimplementation of a master node, such as master node 110 a shown anddescribed with respect to FIG. 4. Vehicle master node 9315 is shownoperative to communicate with server 100 over a longer-rangecommunication interfaces (such as interface 485 on exemplary master node110 a) and operative to communicate with other nodes, such as masternode 9320 associated with storage unit A 9305, master node 9325associated with storage unit B 9310, and other nodes associated withparts of such storage units and node packages stored within the storageunits. In more detail, each storage unit may include, in someembodiments, built-in nodes associated with particular shelves, lockers,receptacles, or other parts of the particular storage unit.

Thus, an exemplary storage unit (such as storage unit A 9305) may be anode-enabled storage unit used within a logistics vehicle to safely andintelligently transport node packages. As such, the exemplary storageunit may itself have a hierarchy of nodes (e.g., a master node, and oneor more other nodes (ID nodes or other master nodes) assigned todifferent parts of the unit) and be operative to detect the location ofparticular node packages via the various location determination methodsdiscussed herein as the node package is placed in a storage locationwithin the unit, moved between storage locations of the unit or betweendifferent units, or simply removed from the storage location within theunit.

As shown in FIG. 20, various node packages 9330 a-9330 d may be kept indifferent storage locations of storage unit A 9305 within vehicle 9300.Similarly, other node packages 9330 e-9330 g are kept in portions ofstorage unit B 9310. Such node packages may be placed into particularstorage locations according to shipping information related to the nodepackages. For example, the node packages may be placed into particularstorage locations according to weights of the particular node packages,a planned loading scheme (such as according to an anticipated deliveryschedule), to storage capacity of the particular different locationswithin the storage unit, or according to a storage type for theparticular different locations (e.g., one location for storing envelopetypes of packages, another location for storing boxed container type ofpackages, another location for storing containerized packages (e.g.,ULDs), etc.).

Shipping of containerized groups of packages (e.g., ULD types ofcontainers made to optimize airborne logistics handling of packages) isan example of where a mobile storage unit (such as a movable unit loaddevice (ULD)) may be deployed when shipping node packages in an airborneenvironment. FIG. 21 is a diagram illustrating exemplary mobile storageunits, such as ULDs, used as containers that help ship node packages inan exemplary airborne environment in accordance with an embodiment ofthe invention. Referring now to FIG. 21, a cut-away perspective view ofan exemplary aircraft fuselage 9400 is illustrated. In particular, anexemplary floor 9405 of a cargo storage area within fuselage 9400 isshown having multiple roller elements that help facilitate movement ofcargo within the cargo area. Additionally, while not shown in FIG. 21,the cargo storage area and floor 9405 typically include structure andfastening points to help hold any cargo loaded within fuselage 9400. Thecargo storage area within exemplary fuselage 9400 may be split into anupper area and a lower area by an additional floor 9410.

The cut-away perspective example illustrated in FIG. 21 shows a lowercargo area where various ULD containers 9420 a-9420 d are shown alongwith an airborne master node 9415, which is (depending on the aircraft'slocation and communication mode and status) operative to communicatewith server 100—much like vehicle master node 9315 does as shown in FIG.20. In general, the illustrated configuration of ULD containers 9420 a-dis used similar to the storage units illustrated and described in FIG.20. For example, each ULD container 9420 a-d may have different storagelocations within it and one or more master nodes (not shown) dedicatedand attached internally so that they may track, monitor, and communicatewith different node packages loaded within the ULD as well as othernodes and a server—much like the master node 9320 for storage unit A9305 can track, monitor, and communicate with different node packagesloaded within the storage unit as well as other nodes and server 100.Node packages within each ULD may communicate with nodes in the ULD andmay communicate directly with airborne master node 9415 directly (orindirectly through other master nodes within the ULD). And as such,shipping information may be used when the node packages are placed intoparticular storage locations within a particular ULD according toweights of the particular node packages, a planned loading scheme forthe ULDs (such as according to an anticipated delivery schedule), tostorage capacity of the particular different locations within the ULD,or according to a storage type for the particular different locations.

Those skilled in the art will appreciate that each of the embodimentsdescribed above related to methods for locating a node may be furtherenhanced when applied to an exemplary vehicular environment. Forexample, in one embodiment, determining a node's location may furthercomprise determining a location of the node-enabled package within avehicle to be the location of the node. In a more detailed embodiment,the method that determines a node location may further generate alocation message regarding where the node-enabled package is locatedwithin the vehicle based upon the determined location of the node. Sucha message may be displayed to a user (e.g., logistics personnel thathandle packages being shipped) on a user interface of a node or useraccess device operating as a node (e.g., smartphone or smart wearabledevice). For example, such a displayed message may be a type of aninformed prompt (“Pickup Package X at Storage Location 01 in StorageUnit A”) or strategic instruction (“Place Package X in Storage Location01 in Storage Unit A”) or (“Move Package X at Storage Location 01 inStorage Unit A to Storage Location 03 in Storage Unit B”). In someembodiments, the network device or node that determines the node'slocation may also provide such a display to the user, but in otherembodiments, the location message may be transmitted to another node fordisplay to the user.

In another embodiment, an exemplary method that determines a node'slocation may also access shipping information related to thenode-enabled package and generate a relocation message regarding wherethe node-enabled package may be relocated within the vehicle based uponthe determined location of the node and the accessed shippinginformation. Such a message may be displayed to a user similar to thelocation message described above—namely, that such a relocation messagemay be displayed to a user (e.g., logistics personnel that handlepackages being shipped) on a user interface of a node or user accessdevice operating as a node (e.g., smartphone or smart wearable device)and that in some embodiments, the network device or node that determinesthe node's location may provide such a display to the user, but in otherembodiments, the relocation message may be transmitted to another nodefor display to the user.

In more detail, the shipping information may comprise weight informationon the node-enabled package that is used in determining where torelocate or initially place the node-enabled package.

In another embodiment, such shipping information may be used to create aloading scheme to help organize where to locate or relocate thenode-enabled packages. Thus, the location or relocation of thenode-enabled package within the vehicle may be determined according to aloading scheme. In more detail, such a loading scheme may be related toan anticipated delivery schedule, where the node-enabled package may beplaced within or removed from the vehicle according to the anticipateddelivery schedule.

Logistics Applications of a Wireless Node Network

As described above, an exemplary wireless node network may be useful ina logistics application where an item is to be located. Further, such anexemplary wireless node network may also be useful in logisticsapplications where the item is moving between locations, and the networkprovides an enhanced level of visibility and management of the itemwithin such a logistics environment. In other words, an embodiment of anexemplary wireless node network in accordance with one or moreprinciples of the present invention helps enable enhanced logisticaloperations that manage information when shipping and tracking an item.FIG. 17 is a diagram illustrating an example logistics operation usingexemplary components of a wireless node network in accordance with anembodiment of the invention.

Logistics Beyond Pickup and Delivery

Referring now to FIG. 17, an ID node 120 a is illustrated as beingdeployed and associated with an item (e.g., package 130) to be shipped.As the package 130 is being prepared for shipping 1700, and is intransit as part of shipment 1705, and is in the possession of theintended recipient 1710, components of an exemplary wireless nodenetwork are deployed to manage information regarding the shipment duringthese three phases.

In a general example of using a wireless node network for managinglogistics related to an item to be shipped, a shipping customer mayinitially register the item (such as package 130) with a node (such asan ID node) to be shipped from an origin location to a destinationlocation. One or more management hand-offs of the item and node occursas the item and the ID node collectively transit a path from the originto the destination. Each hand-off may be based upon an awareness of theshipment path the ID node associated with package 130 will take as it istransferred through a shipping path from its origin to destination.Hand-off of the package 130 and ID node are managed and coordinated withmaster nodes (such as master nodes 110 a-110 h), which are managed byserver 100, along the anticipated shipment path. During operation alongthe shipping path, server 100 receives information and updates fromnodes, manages and authorizes hand-offs between different nodes, andtracks information related to current associations, shared data, sensordata available, locations of the nodes, and context data that helps torefine the location of nodes. Thus, with the ID node associated withpackage 130, the visibility of the package 130 may be extended for thecustomer beyond the conventional custodial control during transit 1705as the shipping customer prepares the item for shipment 1700 prior to aninitial drop-off and after delivery of the item to the recipient 1710.

In a more detailed embodiment, an exemplary method for managinglogistics related to an item to be shipped using a wireless node networkbegins with registering a node with the item to be shipped. For example,the shipping customer may control user access device 200, and use device200 to initially associate an ID node 120 a and package 130 with atracking number as part of preparing to ship the package 130 (a type ofitem). In one embodiment, device 200 may use a particular app or otherprogram module resident and operating on device 200 to input thetracking number of the package 130. Device 200 then provides thatinformation back to server 100 via network 105 to associate the trackingnumber with the package 130 and ID node 120 a. Device 200, in someembodiments, may then print a label for the shipment of package 130 (andID node 120 a). In another embodiment, ID node 120 a may be apre-programmed node with pre-existing shipping and payment relatedinformation associated with it. Further details of a label-less shippingand payment in another embodiment are described below.

Concurrent with this action, the shipping customer may associate ID node120 a with package 130. For example, the shipping customer may place theID node 120 a within package 130 and, in some cases, physically attachthe ID node 120 a to a particular part of package 130. In anotherexample, the shipping customer may place an exterior label on package130 where the label itself includes ID node 120 a. Other examples mayeffectively group ID node 120 a with package 130 within a largerpackage, container, or pallet of items or packages that collectivelytravel together.

In this manner, device 200 may operate as a type of master node undercontrol of the app or other program module, and be associated with thepackage 130 and ID node 120 a from an association managementperspective. For example, device 200 may operate via the app or otherprogram module along with Bluetooth® hardware and software working ondevice 200 to communicate with ID node 120 a. Other embodiments may relyon other short-range communication interfaces for device 200 tocommunicate with ID node 120 a. And in one embodiment, device 200 mayreceive one or more security credentials from server 100 in order toconnect and actively pair or connect with ID node 120 a.

With at least the shipping information at the server 100, server 100 maydetermine a predicted shipping path for the package 130. In oneembodiment, server 100 may have historic data indicating an optimalroute for shipping an item from point A to point B that uses aparticular shipping path (e.g., pick-up near A by a particular courier,transport by vehicle to a particular facility, further transport viaaircraft to another facility near point B, and transport by vehicle tofacilitate delivery by a courier at point B). In one example, thepredicted path may only be for a portion of the route between twopoints, such as an origin point and a destination point.

In a further example, the predicted path (or part thereof) may beadjusted based on the contextual environment of an item being shipped.For instance, depending on context data (such as weather information,historic data on success for particular transit segments, capacityinformation for third party carriers, etc.), server 100 may alter theinitially predicted shipping path to provide a refined predictedshipping path that is more optimized under the current conditions andcontext. This allows the server 100 to further anticipate which masternodes may be used along an anticipated shipping path (or refinedshipping path), to help efficiently manage shipment of the package 130to point B. Those skilled in the art will further appreciate that anembodiment may only partially identify what master nodes may be usedalong the anticipated shipping path (or refined shipping path), and thatfurther master nodes may be identified as the package 130 is actively inroute to point B depending on context data (e.g., master nodeavailability, weather information, etc.).

In a more detailed example, server 100 may use sort data analytics topredict an appropriate shipping path along which the package 130 and theID node 120 a will travel, identifying predicted master nodes the IDnode 120 a will be within range of during its journey. In the exampleflow illustrated in FIG. 17, nodes 110 a-110 h refer to different masternodes along an exemplary predicted shipping path, which includes atleast a pick-up and drop-off of ID node 120 a and package 130 at anorigin and destination, respectively.

In one example, the shipping customer may place package 130 and itsassociated ID node 120 a in a drop box or repository for items to beshipped. In the illustrated example of FIG. 17, drop box is representedas drop node 110 a. Essentially, drop node 110 a may be implemented witha type of master node connected to or integrated into a drop box orlocker unit type of logistics repository (more generally referred toherein as a node-enabled logistics receptacle). As the shipping customerphysically places ID node 120 a into drop node 110 a, device 200 mayhand-off ID node 120 a to drop node 110 a, update server 100 with thisassociation information, and disassociate from ID node 120 a. In thismanner, the system has visibility into the status and location of anitem (such as package 130) prior to pick-up from drop node 110 a.Further details of an exemplary node-enabled logistics receptacle aredescribed below.

At the drop node 110 a, a courier may pick-up the package 130 and IDnode 120 a. The courier has a courier node 110 b, which knows thetracking number and associated ID node 120 a at time of pickup, or looksup the ID node 120 a MAC address based on a captured tracking number(part of information broadcast or advertised by ID node 110 a.Basically, the master node responsibility transfers to or is otherwisehanded off to courier node 110 b, which now acts as a master nodeactively connected and associated with ID node 120 a (by virtue ofcommunications from courier node 110 b back to server that authorizesthe association of ID node 110 a with courier node 110 b anddisassociates drop node 110 a with ID node 110 a).

Similar handoffs occur between different master nodes and ID node 120 aoccur as package 130 and ID node 120 a transit the anticipated shippingpath in accordance with instructions sent to different master nodes byserver 100. In one embodiment, associations are accomplished during suchhandoffs with security credentials requested, authorized, andtransmitted to the appropriate master node. In another embodiment,associations are merely passive associations that do not require activeand authorized pairings. Yet, the passive association still may allowthe system to keep track of ID node 120 a and package 130 as theytransit the anticipated shipping path.

New associations (active and passive) and disassociations are updated toserver 100. And server 100 may change programming in different nodes aspackage 130 and ID node 120 a transit the shipping path—such as changingthe operation of a master node (such as ULD node 110 e) to shift tooperating as an ID node while airborne or when GPS signals are lost. Inanother example, certain mobile types of node may have responsibilitieschanged to wired types of nodes as a way of preserving the power of amobile type of node. If ID node 120 a fails to associate for a certaininterval and needs to be reacquired, ID node 120 a may update its statusflag to a particular Alert Stage and may attempt to communicate with anincreasingly broader range of master nodes in order to be found.

During the transit, server 100 may share information with differentnodes, such as context data, timer/clock data, environmental data, etc.Sensor data from the ID node 120 a may be gathered via scans from amaster node, and then forwarded back to server 100. And as server 100manages the associations, handoffs, and information going to and comingfrom ID node 120 a (via master nodes), server 100 is able to determinethe location of ID node 120 a using one or more of the various locationdetermination techniques described above. As such, server 100 is able toprovide information related to the ID node 120 a and its related package130 in response to requests for such information.

When package 130 and ID node 120 a arrive at the destination (e.g.,point B), courier node 110 h may update server 100 once ID node 120 a isplaced at the destination and disassociated with courier node 110 h.However, visibility need not end at such a drop-off event (such asarriving at the destination). The recipient customer's user accessdevice 205 may act as another master node, and associate with ID node120 a after delivery. In one example, server 100 is notified by couriernode 110 h that delivery has been made. Thereafter, server 100 maynotify device 205 with this information. In response, an app or otherprogram module on device 205 may cause device 205 to operate as a nodeand to actively seek association with ID node 120 a. When device 205 andID node 120 a connect and are given authorization by server 100 toactively associate, server 100 is notified and may provide furtherinformation to device 205 (e.g., sensor data, etc.) and may be able todetermined updated location data about ID node 120 a and package 130after delivery has occurred. In another example, active association maynot be needed between device 205 and ID node 120 a as status informationmay still be gathered by device 205 via passive association, where thestatus information provides further visibility regarding the ID node 120after delivery to the destination.

FIGS. 18 and 19 are flow diagrams illustrating various exemplary methodsfor managing a shipment of an item using a wireless node network, suchas that illustrated in FIG. 17. Referring now to FIG. 18, exemplarymethod 1800 begins by transmitting shipping information to the server toregister the ID node and the item to be shipped at step 1805 andassociating the ID node to a first master node related to a predictedpath for shipping the item at step 1810. At step 1815, the server isupdated to reflect the association between the ID node and the firstmaster node. Typically, this may come in the form or a communicationfrom the first master node to the server. When the first master node isa user access device (e.g., one of a laptop computer, a desktopcomputer, a tablet device, a personal area network device, a smartphonedevice, and a smart wearable device) that is operated by a shippingcustomer, the server may be updated to become aware that the ID node isassociated with the first master node prior to a pick-up event in thepredicted path.

For example, a shipping customer may use their smartphone to entershipping information and register that the ID node and the item (such aspackage 130) are to be shipped from an origin point to a destinationpoint. Prior to when the item and ID node are picked up by an initialcourier (e.g., from a drop box, locker unit, or other receptacle), theshipping customer's smartphone operates as the first master node and isassociated with the ID node. As such, and with an update to the server,the server now has visibility into the status and location of the IDnode prior to a pick-up event in the predicted shipping path from theorigin point to the destination point.

The method 1800 may continue at step 1820 by disassociating the ID nodeand the first master node when associating the ID node and a secondmaster node related to the predicted path as the ID node transits thepredicted path. In one example, the ID node need not disassociate withthe first master node commensurate with associating with the secondmaster node. Thus, those skilled in the art will appreciate that the IDnode may be associated with one or more master nodes at a given point intime and may be selectively disassociated with certain master nodesdepending on the need for the ID node to securely share data withdifferent master nodes.

At step 1825, the server is updated to reflect the disassociationbetween the ID node and the first master node (if that has occurred yet)and the association between the ID node and the second master node asthe ID node continues to transit the predicted path. At step 1830, themethod may associate the ID node to a third master node near an end ofthe predicted path for shipping the item, and then at step 1835 notifiesthe server to reflect the association between the ID node and the thirdmaster node.

In the method 1800, associating the ID node to the third master node instep 1830 may be performed after a drop-off event in the predicted path.The method may also rely upon context data to adjust for anenvironmental aspect of the predicted path when associating the ID nodeto any of the first, second, or third master nodes.

For example, after the item and ID node are delivered to or near thedestination, the recipient's smartphone may operate as the third masternode associated with the ID node. Data, such as sensor data, may beshared with the recipient while the recipient's smartphone operates asthe third master node associated with the ID node. As such, and with anupdate to the server, the server now has visibility into the status andlocation of the ID node after a drop-off event.

Thereafter, the recipient may unregister the ID node and item given theitem is now in the recipient's possession and control. For example, therecipient may remove the ID node from the item (e.g., the package 130),deactivate the ID node to otherwise power down the device, update theserver regarding the deactivated status of the ID node (and thedisassociation of ID node and the third master node), and then clean upand/or recharge the ID node for future use in shipping another item.

Method 1800 may also include receiving context data related to thepredicted path. In one embodiment, such context data may advantageouslyallow for adjustments due to one or more environmental aspects of thepredicted path when associating the ID node to any of the master nodes.For example, the context data may include scan data indicating the typeof material in package 130 (the item), which may cause RF shieldingissues with the ID node.

Referring now to FIG. 19, exemplary method 1900 is explained from theperspective of the server, which can authorize certain types of nodeassociations. The server may be updated, in some embodiments, withassociation information when an ID node and a master node are passivelyassociated. In such a situation, the nodes have not established anauthorized association where they can securely share data. However, asmethod 1900 explains in more detail, an embodiment may manage a shipmentof an item when active associations are established.

Method 1900 begins with the server receiving shipping information toregister the ID node and the item to be shipped in step 1905. The method1900 then provides a first set of authentication credentials (e.g.,security pin information) to a first master node to permit the ID nodeto associate with the first master node related to a predicted path forshipping the item at step 1910. In one example, the first master nodemay be a user access device, such as a laptop computer, a desktopcomputer, a tablet device, a personal area network device, a smartphonedevice, or a smart wearable device. And step 1920 may be performed priorto a pick-up even in the predicted path.

At step 1915, the server receives an update to reflect the associationbetween the ID node and the first master node. The method 1900 thenprovides a second set of authentication credentials to a second masternode to permit the ID node to associate with the second master node anddisassociate the ID node from the first master node as the ID nodetransits the predicted path at step 1920. At step 1925, the server thenreceives an update to reflect the association between the ID node andthe second master node as the ID node continues to transit the predictedpath (or a portion of a predicted path). When the ID node and the firstmaster node disassociate, the server may also be updated.

In some examples, the method 1900 may have the server provide a thirdset of authentication credentials to a third master node to permit theID node to associate with the third master node as the ID node reachesan end of the predicted path for shipping the item at step 1930. In someexamples, this step may be performed after a drop-off event in thepredicted path.

Finally, at step 1935, the server receives a notification that reflectsthe association between the ID node and the third master node. When theID node and the second master node disassociate, the server may also beupdated.

In method 1900, another embodiment has the server providing any of themaster nodes with context data related to an environmental aspect of apart of the predicted path. For example, exemplary context data mayinclude layout data related to a facility in which the ID node is movingbetween master nodes. In more detail, the received context data may berelied upon to adjust for an environmental aspect of the predicted pathwhen associating the ID node to any of the first, second, or thirdmaster nodes.

In still another embodiment, method 1900 may also determining a locationof the ID node based upon association information received by the serverand location information related to at least one of the first, second,or third master nodes.

As previously discussed, the server may predict a transit route from afirst point to a second point along at least a portion of the predictedpath for shipping the item. In one example, the first point is an originand the second point is a destination point with both being identifiedin the shipping information of the item. However in other examples, thefirst and second point along a predicted path may merely be interimpoints without encompassing the originating shipment point or theultimate destination of the item being shipped. Further, another examplemay adjust the predicted path as the ID node transits the path. In thisway, the server may adapt based upon, for example, context data, so asto optimize or at least account for a changing contextual environmentwhen managing the shipment of an item.

In another embodiment, a non-transitory computer-readable medium isdisclosed that contains instructions, which when executed on a processor(e.g., processor 500 of server 100), performs another embodiment of amethod for managing a shipment of an item using a wireless node networkhaving at least one ID node, a plurality of master nodes, and a server.In this embodiment, the exemplary method begins with the serverreceiving shipping information to register the ID node and the item tobe shipped. The method predicting a first portion of a transit route forthe item from a first point to a second point. For example, a firstpoint may be the origin point and the second point may be thedestination point—both of which are identified in the shippinginformation. In another example, the first and second points are any twopoints along the transit route. Furthermore, the transit route may bepredicted as a series of portions or segments that may use particulartypes of master nodes during transit (e.g., master nodes used by aparticular courier for pick-up, an anticipated vehicle used by thepickup courier, one or more anticipated facilities that may be used bythe vehicle, an anticipated air route (e.g., an anticipated departingairport, an anticipated aircraft, anticipated types of containers suchas a type of ULD or pallet used on the aircraft, and an anticipatedarriving airport), a facility near the anticipated arriving airport, avehicle used to carry the item, and a courier that may deliver the itemat the destination point). Those skilled in the art will realized thatsome of the potential portions of an exemplary predicted path or transitroute may be relatively simple for a local delivery, or may be quitecomplex from an intermodal perspective when the origin point anddestination points are very far away from each other.

Next, the method authorizes a first master node to associate or connectwith the ID node near the origin point. This may be done prior to apick-up event for the ID node and item being shipped. For example, whenthe first master node is a user access device (e.g., a laptop computer,a desktop computer, a tablet device, a personal area network device, asmartphone device, and a smart wearable device) for the shippingcustomer, visibility as to the status and location of the ID node may beextended to prior to a pick-up event. In one embodiment, such anauthorization is performed by the server 100 when it receivesinformation from the first master node regarding the ID node, determinesthat the first master node and the ID node should be actively paired andassociated, and the server 100 sends the appropriate security pininformation as a type of authorization credentials that permit the firstmaster node to actively pair and connect with the ID node. After thefirst master node is associated with the ID node, the server receives anupdate reflecting the association.

Next, the server may authorize a second master node to associate withthe ID node as management responsibility of the ID node is handed offfrom the first master node to the second master node at the second pointon the predicted transit route. In one embodiment, the method mayauthorize the first master node to disassociate with the ID node.However, in other embodiments, the first master node may stay associatedwith the ID node—even after the ID node is authorized to associate withthe second master node. The server then receives an update to reflectthe association between the ID node and the second master node as the IDnode continues on the predicted first portion of the transit route.

The method may further authorize the second master node to disassociatewith the ID node and a third master node to associate with the ID nodeas management responsibility of the ID node is handed off from thesecond master node to the third master node near the destination pointon the predicted transit route. This may be done prior to a pick-upevent for the ID node and item being shipped. For example, when thethird master node is a user access device (e.g., a laptop computer, adesktop computer, a tablet device, a personal area network device, asmartphone device, and a smart wearable device) for the recipient,visibility as to the status and location of the ID node may be extendedto after a drop-off event. After the third master node is associatedwith the ID node, the server receives a notification to reflect theassociation between the ID node and the third master node.

And during the method, the server may determine a location of the IDnode based upon association information received by the server andlocation information related to at least one of the first, second, orthird master nodes. As discussed above, various techniques are availablefor locating a node and, in some cases, adjusting for adverse RFenvironmental conditions with context data to more accurately refine thelocation of a node. As such, the server keeps track of the location ofnodes in the wireless node network, and may provide that information (aswell as other types of shared or sensor information) when requested andauthorized to do so.

From a system perspective of such a logistics application of a wirelessnode network, an exemplary system is disclosed for managing a shipmentof an item using a wireless node network. With reference to FIG. 17, theexemplary system generally comprises an ID node (such as node 120 a), aplurality of master nodes (such as nodes 110 a-110 h), and a server(such as server 100). The ID node is registered to the item (such aspackage 130) being shipped. Each of the master nodes are predicted to belocated at a different part of an anticipated transit route for the itemas the item is shipped from an origin point to a designation point ofthe anticipated transit route. Each of the master nodes is operative tocommunicate with the ID node over a short-range communication path, andoperative to communicate with other master nodes and the server 100.

The server operates to track and report a location of the ID node and alocation of the master nodes. As shown in FIG. 17, server 100 relies onnetwork 105 to communicate with different master nodes (110 a-110 h) aswell as user access devices 200, 205 that may operate and function as amaster node associated with ID node 120 a at certain times. Aspreviously discussed, server 100 may employ a variety of differenttechniques (or a combination of different techniques) for determiningthe location of ID node 120 a or one of the other nodes in the network.

The server is also operative to facilitate the transfer of managementresponsibility of the ID node between different master nodes as the IDnode moves along the anticipated transit route. For example, asdiscussed above, nodes communicate via broadcast and scanning methods,and may be associated under control of the server 100 as part ofmanaging the wireless node network. In this way, a first of the masternodes may be associated with the ID node prior to a pick-up event forthe ID node and item to be shipped. In one example, user access device200 may operate as a master node and be associated with ID node 120 aprior to being placed into drop node 110 a and picked up by a courierfrom the receptacle related to that drop node 110 a.

Later, a second of the master nodes may be associated with the ID nodeafter the ID node is disassociated with the first of the master nodes atan intermediate point of the anticipated transit route. And, a third ofthe master nodes may be associated with the ID node after a drop-offevent for the ID node and item to be shipped. For example, user accessdevice 205 may operate as a master node and be associated with ID node120 a after the ID node 120 a and item are dropped off at an intendeddestination point (e.g., a type of drop-off event).

In an embodiment of the system, each of the master nodes may beoperative to update the server upon completing a disassociation orassociation with the ID node. This provides the server with associationinformation with which it can use to manage and track the nodes in thewireless node network. When associating nodes, the server may beoperative to transmit a set of authorization credentials to one of themaster nodes and the ID node to authorize a desired association betweenthe master node and the ID node. The server may also be operative todetermine the location of the ID node based upon context data, such asinformation relating to an environmental aspect of a part of theanticipated transit path (e.g., RF shielding aspects of the item beingshipped with the ID node or a container holding the ID node, buildinglayout information, etc.).

Those skilled in the art will readily appreciate that operations of suchan exemplary wireless node network, as set forth herein, are not limitedto tracking just a package, but may be used to manage logistics andtracking of other types of items, such as an object or a person. Indeed,some embodiments provide enhanced capabilities that facilitate bettertracking of items, objects, and people as they move to a morerestrictive indoor environment, by using a low power ID node inadvertising mode in the presence of one or more master nodes.

Enhanced Monitoring & Network Management Based Upon Event Candidates

As described above, various elements of an exemplary wireless nodenetwork may have certain roles and responsibilities in an embodiment forintelligently monitoring and managing the nodes in the wireless nodenetwork using a context-driven, learning framework. One embodiment ofsuch a framework may deploy a master node to listen for signalsemanating from different ID nodes in a general vicinity of the masternode as an exemplary element of the wireless node network that monitorsthe ID nodes. The master node may detect signals from a particular IDnode, track a series of such signals relative to the particular ID node,compare observed parameters related to such signals (or summarizedrepresentations of the signals or statistical representations of thesignals generally referred to as checkpoints) to identify a status ofthe ID node (more generally referred to as a node event for the ID nodeindicating what is going on with the ID node). If appropriate undercertain event criteria, the master node may deem the identified statusimportant enough to selectively report the identified status back up toa server, in contrast to simply providing all captured signals or allsummarized or statistical representations of such signals to the server.This advantageously helps manage data communication traffic between themaster node and server during monitoring operations and helps avoidoverburdening the server. Upon receiving the selective report from themaster node, the server may then process information related to theidentified node event to determine if the reported informationcorresponds to known node activity (such as a known source of RFinterference or entering into a known structure that attenuates RFcommunication signals) and, if appropriate, adapt how the server managesthe network via updates to node management information (such as contextdata indicating the source of the RF interference) and providingmanagement feedback delivered back to the managing node. In such a way,an embodiment may have the managing node (e.g., a master node) and aserver operate as part of a monitoring and learning system that adaptsto what is being experienced by a lower level node in the system in aparticular manner of monitoring, selective reporting, assessing thereported information, and adapting to the reported information withupdated context data and updated feedback to nodes in the system.

As noted above, a monitored or observed status related to a node may begenerally referred to as a node event. A node event for a node mayinclude, for example, a status of whether the node has been detected bythe monitoring node, a status indicating how the node is communicatingwith the monitoring node, a status on what information the node iscommunicating or broadcasting, and an update on the node's status (e.g.,whether the observed status has changed reflecting movement toward oraway from the monitoring node) as identified by the monitoring node(typically a master node). In some of the embodiments described below,monitoring for node events may involve a variety of different types ofexemplary events related to a particular ID node—e.g., a first sightingevent, a sporadic event, an online event, an offline event, a checkpointevent, a benchmark checkpoint event, and a shift event. In anembodiment, such exemplary events may represent a current or updatedstatus of a broadcasting node as observed by a master node and, in someembodiments, may involve observing particular parameters of an ID node'sadvertising signal as received by the master node (e.g., an observedRSSI level of a detected advertising signal that is being broadcast froman ID node over time, an observed setting or indicator as reflected inheader information within a detected advertising signal) or a particularchange in such an observed parameter (e.g., a significant change ofobserved timing, a change of observed signal strength level of thedetected advertising signal, a change of data broadcast by the ID nodethrough data in the advertising signal packet).

Those skilled in the art will appreciate that monitoring for node eventsmay generate very large amounts of scan data over time. For example, anembodiment may have a master node in a scanning or listening mode anddetect a large number of advertising signals successively broadcast overtime from one or more ID nodes as the ID nodes move relative to themaster node. Monitoring of nodes for node events in such an embodimentmay involve comparing one or more observed parameters from differentscan data detected (e.g., different detected advertising signalsbroadcast from one of the ID nodes). The comparison may involvecomparing an observed parameter, such as observed signal strength,related to two detected advertising signals broadcast from a particularID node while in other embodiments, the comparison may involve comparingan observed parameter related to summarized representations of groups ofdetected advertising signals. Such a comparison allows the monitoringnode to learn of the node event related to the ID node, and whenappropriate based upon certain event criteria, report such a node eventback to a server as a reported event candidate, which includes eventdata relative to the ID node's status (e.g., the node event reflecting achanged status or simply an updated status for the particular ID node).

As noted above, in some embodiments, the monitoring node may capture andanalyze the received scan data (e.g., detected advertising signals) as aseries of summarized checkpoints over time. Each checkpoint may beconsidered a summarized representation of the detected signals over aparticular time period or relative to a particular number of detectedsignals. In some embodiments, each checkpoint may further be considereda statistical representation (e.g., a mean, a median, an average, amoving average over a subset window of advertising signals, a movingaverage over a sliding time window, or a weighted average) ofobservations of the detected signals over the particular time period.For example, the monitoring master node may generate a checkpoint (alsogenerally referred to as a checkpoint summary) that summarizes tendetected signals at a time. The observed parameter for the checkpointmay, for example, represent an average of the observed signal strengthfrom each of the ten successively detected advertising signals from anID node. As such, the master node may identify an event candidate basedupon comparing the observed parameter of the signals associated with thecheckpoint with the observed parameter of a prior checkpoint, ratherthan just comparing the observed parameter related to two or moredetected signals. Comparing checkpoints (rather than comparing eachdetected signal) may allow the monitoring node to better accommodatenoisy environments and more selectively identify a node event as anevent candidate based upon adjacent checkpoints, and when appropriate,report such an event candidate back to a server with relevant event datainformation about the particular checkpoint where the node event wasidentified. Thus, a general embodiment compares an observed parameterbetween detected signals where other embodiments may further process thedetected successive signals, as a group, to then compare the observedparameter (such as observed signal strength) of a summarized or otherstatistical representation of successive groups.

An embodiment that monitors for event candidates may use a master node(such as the master node 3410 illustrated and described with respect toFIGS. 34 and 35) to receive, monitor, detect, or otherwise observeadvertising signals broadcast by various nodes (e.g., ID nodes or othermaster nodes) so that information related to different types of on-goingnode events may be captured, summarized (in some instances), assessed,and selectively reported to the backend server as an event candidates(e.g., a type of summarized data related to a node event). Those skilledin the art will appreciate that the manner in which an exemplary masternode may advantageously summarize and simplify how to analyze andselectively report relevant node event information as the eventcandidate enables an improved efficiency of master node to serverinteractions related to monitoring event candidates in such a system andenhances system operations by not overloading the server via a reduceddata feed from the master node while monitoring in such a manner.

Additional embodiments may use the backend server (such as the server3400 illustrated and described with respect to FIGS. 34 and 36) to applya process that ranks or scores the received event candidate to determinehow closely the event correlates with other server-accessible datarepresenting known node relevant activity. Based on such a confidencetype of ranking or scoring, the backend server may learn about what ishappening to nodes and, in some cases, packages associated with nodes,and may then adjust, change or refine node management information (suchas relevant node management context data and/or relevant node managementrules data) used to help manage other elements of the network. Forexample, based upon a reported event candidate, the server may providefeedback to the master node to alter or otherwise update how the masternode operates itself and/or how the master node manages one or more ofthe ID nodes under its control via updated context data or updated nodemanagement rules (e.g., revised operational profiles the define how amaster node and/or ID node functions, operates, reports to other nodes,etc.). Such updated node management rules may also identify new noderelated or node relevant activity (e.g., a motor turning off near anode, a vehicle driving by a node, a node being exposed to some type offacility structure that may impair communications temporarily) forfurther investigation. Thus, the server may operate as the core of atype of learning system based on observations from the master node and aconfidence factor determined by the server relative to whether certainobservations appropriately correspond to particular node relatedactivities so that the server can more accurately be aware of changesrelated to the dynamic status of nodes and respond accordingly.

In other words, embodiments may deploy a system having the master nodemonitoring for an event candidate related to an ID node along with abackend server that deploys analytics-based processing where eventcandidates may be ranked for confidence of being correlated to known ornew node relevant activity as a type of input for improved server-basedmanagement of nodes in the network and enhanced quality/efficiency ofhow node event information may be captured and reported as a basis forwireless node network management.

A general embodiment of such an exemplary system that monitors for anevent candidate (via detected signals and/or summarized representationsof such signals in the form of checkpoints) and processes reported eventcandidates as part of managing the wireless node network is illustratedin FIG. 34. Referring now to FIG. 34, the exemplary networked systemshown is similar to that shown in FIGS. 1 and 2 but with further detailson how monitoring and managing may be accomplished. In particular, FIG.34 illustrates that the network includes a server 3400 connected to anetwork 105, which is also operatively connected to different networkcomponents, such as a master node 3410, and connected indirectly toother network components (such as different ID nodes through master node3410). Some of the exemplary ID nodes in communication with master node3410 (i.e., nodes 120 a and 120 e) are illustrated outside of acontainer 3420, while the remaining ID nodes (i.e., nodes 120 b-120 d)are shown disposed within container 3420.

In the system embodiment shown in FIG. 34, master node 3410 is executingevent detection engine code 3415 to specially adapt the master node 3410into an enhanced apparatus (as part of the system) that monitors forevent candidates related to one or more of the ID nodes (e.g., one ormore of ID nodes 120 a-120 e) that may be in communication with masternode 3410. When master node 3410 detects an advertising signal from oneof the ID nodes shown in FIG. 34, master node 3410 may track timing andobserved signal strength values (such as RSSI values) for this firstadvertising signal and any in a series of successively broadcastedadvertising signals in what may be considered an observation window orevent horizon related to that ID node. Master node 3410 may identify anevent candidate during the event horizon (e.g., at the beginning whendetecting the first advertising signal, during on-going monitoring ofthe successive signals, while observing significant shifts or changes inaspects or parameters related to the detected advertising signals, whileno longer detecting further signals in the series, etc.). Master node3410 may identify the event candidate during the event horizon basedupon a comparison of detected advertising signals or, in someembodiments, a comparison of different checkpoint summarizations ofgroups of successively detected advertising signals.

Once a node event is identified to be an event candidate that should bereported back to the server, master node 3410 may report the eventcandidate to server 3400 in a simplified data feed to server 3400reflecting summarized information on the status of the broadcasting IDsignal (in contrast to reporting all observations on the detectedadvertising signals). As shown in FIG. 34, Server 3400 is executingevent candidate analytics engine 3405 to specially adapt the server 3400into an enhanced apparatus (as part of the system) that processes thereported event candidates received from master node 3410 as a part ofcorrelating the event candidate to node relevant activity as alreadycharacterized by data maintained on the server (e.g., where a node eventreflecting a shift in RSSI values can be correlated to node relevantactivity of an ID node passing through a shielded tunnel).

FIG. 35 is a detailed diagram of exemplary master node 3410 as shown inthe network illustrated in FIG. 34 that operates to monitor for an eventcandidate to be reported to a server in accordance with an embodiment ofthe invention. Referring now to FIG. 35, exemplary master node 3410 isillustrated at a level of detail similar to that as shown and explainedabove for master node 110 a in FIG. 4, and includes similar componentelements as those appearing in master node 110 a and explained withreference to FIG. 4 (where similarly labeled elements are generally thesame). However, FIG. 35 illustrates exemplary master node 3410 as havingadditional software and additional types of data used in embodimentsthat provide enhanced monitoring for an event candidate.

In particular, exemplary master node 3410 has memory storage 415 andvolatile memory 420 that includes event detection engine code 3415. Ingeneral, event detection engine code 3415 comprises a program modulethat may work in conjunction with portions of the master control andmanagement code 425 executing on processing unit 400 to detectadvertising signals through the short range communication interface 480(e.g., via a code section that coordinates with the node advertise andquery (scan) logic manager of code 425), identify event candidates basedon particular observations of the advertising signals, and cause themedium/long range communication interface to report the identified eventcandidates to server 3400 (e.g., via a code section that coordinateswith the information control and exchange manager of code 425).

Similar to what is explained with respect to master node 110 a in FIG.4, exemplary master node 3410 as shown in FIG. 35 may generate and usedifferent types of data stored within memory storage 415 and volatilememory 420. In particular, when event detection engine code 3415 isrunning on processing unit 400, an embodiment may generate and/or relyupon types of event data 3500 when attempting to monitor for eventcandidates. In one embodiment, event data 3500 may generally beconsidered data related to observations of signals from nodes that mayindicate a particular type of node event. Exemplary event data 3500 mayinclude various types of measurement information, such as timinginformation and observed signal strength information, which collectivelyserve to characterize the status of a node from the perspective of oneor more observed parameters of a detected signal from the node. Forexample, such measurement information may include timestamp informationindicative of a time for a first sighting of an advertising signalbroadcast by one of the ID nodes within range of master node 3410; timerinformation indicative of an elapsed time (e.g., as provided byclock/timer 460); a count of how many signals broadcast by such an IDnode have been detected within a particular time frame (such as before aparticular time between signals elapses beyond a predetermined gap timeor over a particular event horizon of time after a first sighting orbetween specific types of events as determined by clock/timer 460 orprocessing unit 400 itself); and an observed signal strength value(e.g., an RSSI value), which may be an actual value or an average typeof value, such as a moving average that helps to smooth out spuriousobserved signal strengths. Further embodiments of event data 3500 mayalso include threshold information related to the measurement type ofinformation (e.g., counter values, time values, level values).Additionally, embodiments of event data 3500 may include a nodeidentifier related to the ID node broadcasting the advertising signaldetected as well as information originating from the identified node,such as a current battery voltage of the node (a type of sensor data), atemperature value associated with the node (another type of sensordata), and payload data provided by the node via the broadcasting signaldetected by master node 3410 through short range communication interface480. Those skilled in the art will further appreciate that such eventdata 3500 may also include similar types of information related tocheckpoint summaries of groups or sets of detected advertising signals.

An embodiment of master node 3410 useful as a monitoring node may beimplemented based upon an Intel® Edison platform computing device. Thoseskilled in the art will appreciate that the Intel® Edison platformcomputing device includes a dual-core CPU and single coremicrocontroller that supports integrated wireless signal monitoring andcommunications having multiple communication interfaces (e.g., Wi-Fi,Bluetooth Low Energy), and data collection in a low power package havingmultiple multiplexed GPIO interfaces with expansion board options fordesired flexibility and scalability for the particular embodiment of amaster node 3410.

Based upon observations of signals received through short rangecommunication interface 480, an embodiment of master node 3410 mayreport a summary of certain event data as an event candidate to server3400. FIG. 36 is a more detailed diagram of exemplary server 3400 in thenetwork illustrated in FIG. 34 that operates to receive an eventcandidate and manage the network based upon the event candidate inaccordance with an embodiment of the invention. Referring now to FIG.36, those skilled in the art will appreciate that exemplary server 3400is illustrated at a level of detail similar to that as shown andexplained above for server 100 in FIG. 5, and includes similar componentelements as those appearing in server 100 and explained with referenceto FIG. 5 (where similarly labeled elements are generally the same).However, FIG. 36 illustrates exemplary server 3400 (in like manner asmaster node 3410 shown in FIG. 35) as having additional software andadditional types of data used in embodiments that provide enhancedmanagement of the network in response to receipt of an event candidatefrom master node 3410.

In particular, exemplary server 3400 has memory storage 515 and volatilememory 520 that includes event candidate analytics engine code 3415. Ingeneral and as explained in further detail below, an embodiment of eventcandidate analytics engine code 3415 comprises a program module that maywork in conjunction with portions of the server control and managementcode 525 executing on processing unit 500 (e.g., via a code section thatcoordinates with the context-based node manager of code 525) tocorrelate or verify the received event candidate information 3600,update appropriate node management information 3605, and generate a typeof responsive feedback for master node 3410 in the form of a managementmessage having at least some of the updated node management information3605. In this manner, exemplary event candidate analytics engine code3415 specially adapts the operations of server 3400 to enhancemanagement of the network. Such enhanced management allows the server3400 to essentially learn from the reported event candidate (based on apredictive scoring or ranking of confidence that the event candidate isactually representative of a node relevant activity), and to provideimproved feedback control for particular node elements based on what islearned.

Exemplary node management information 3605 is generally node managementdata and/or node management rules related to one or more of the nodeelements in the wireless node network. For example, exemplary nodemanagement data may be implemented by context data 560 as shown in FIGS.5 and 36 and, as explained above, may generally relate to what a similarnode (master node or ID node) has experienced in a similar environmentto what a given node is presently experiencing or is anticipated toexperience. Exemplary node management rules may be implemented by ruledata 3610, which generally defines one or more parameters of anoperational profile for a node. For example, rule data 3610 may includea parameter on how long master node 3410 should stay broadcasting at aparticular power level, or how master node 3410 should more quicklyreport event candidates, or how master node 3410 should cause ID node120 a increase its broadcast power level (e.g., a change to profile data530 as it relates to ID node 120 a). As such, node management data (suchas context data 560) and node management rules (such as rule data 3610)are examples of node management information 3605 relied upon and updatedby server 3400 as part of causing nodes in the network to changeoperation in response to reported event candidates.

Master Node Operations Related to Enhanced Monitoring for an EventCandidate

In light of the system embodiment shown in FIG. 34 and details regardingmaster node 3410 and server 3400, as shown in FIGS. 35 and 36, anexample event horizon being monitored by master node 3410 may beexplained where master node 3410 observes, for example, timing andobserved signal strength parameters related to detected ID nodeadvertising signals. In general, an embodiment of master node 3410 mayenter a scanning mode where it listens for advertising signals broadcastfrom nearby ID nodes and then monitors for successive additional signalsor summarized groups of successive additional signals during the eventhorizon that follows after the first signal sighting. FIGS. 37A-37M area series of graph illustrations that show an exemplary timeline ofdetected signals and different types of exemplary event candidates thatmay be identified by a master node, such as master node 3410, over timein accordance with an embodiment of the invention.

Referring now to FIG. 37A, the graph illustrated includes a horizontalaxis and a vertical axis. The horizontal axis represents points in time(e.g., t₀-t₈) progressing to the right. The vertical axis represents anexemplary observed parameter of signals detected by master node 3410(e.g., the observed RSSI value of an advertising signal broadcast by anID node, such as ID node 120 a, and received by master node 3410). Thus,as an advertising signal from ID node 120 a is detected by master node3410 over time, the graph of FIG. 37A shows various data pointsrepresenting successive detections and relevant interpretation of suchdetections by master node 3410.

In particular, master node 3410 detects an initial advertising signalfrom ID node 120 a at point 3700 at time t₀. Master node 3410 identifiesthis initial detection as a first sighting event, which may be reportedto the server 3400 as a type of event candidate. Thereafter, asindicated on the graph of FIG. 37A, further successive signals aredetected within a gap time of each other up to point 3705. The pointsshown on the graph between 3700 and 3705 represent observed RSSI valuesfor the respective ones of the successive signals as the successivesignals are detected. Thus, the graph indicates types of event data 3500and how the master node 3410 observes timing and signal level parametersrelated to the successively detected signals as a basis for such eventdata 3500.

When master node 3410 has detected a predefined sample number, n, of thesuccessive signals, master node 3410 may generate a first moving averageof the observed RSSI values within a sample window at point 3710involving the observed RSSI values from the last n detected ones of thesuccessive signals. At this point, master node 3410 identifies point3710 as an online event, which may be reported to server 3400 as a typeof event candidate. Point 3710 may also be considered as a beginningcheckpoint type of event that represents a summary status of theobserved RSSI values in the form of the first moving average(representing an initial summarized status of the ID node 120 a). Insome embodiments, master node 3410 may not use a moving average of theobserved RSSI values and, instead, may rely upon other statisticalrepresentations of observed RSSI values for groups of detected signals.

As will be explained in more detail below, consideration and reportingof checkpoint events helps master node 3410 avoid overwhelming server3400 with reported events and, instead, advantageously allows fortracking and reporting with summarized information to help simplify thedata feed provided by master node 3410 about the status of ID node 120a.

In FIG. 37B, the same graph continues to reflect operations of masternode 3410 that detect further successive advertising signals from IDnode 120 a and where the actual observed RSSI value and the movingaverage of observed RSSI values are reflected over time from point 3715.At point 3720, master node 3410 has detected a further n number ofsuccessive signals since the beginning checkpoint event at point 3710(each detected within a time gap of each other up to point 3720). Assuch, master node 3410 identifies point 3720 as another checkpointevent, which may be reported to server 3400 as a type of eventcandidate. In other words, an embodiment may have master node 3410utilize checkpoint events or summaries (such as this first checkpointevent also labeled the online event) as a way to periodically summarizeand simplify observations by master node 3410 representing a status ofnode 120 a.

In FIG. 37C, the graph reflects operations of master node 3410 thatdetect still more successive advertising signals from ID node 120 a andwhere the actual observed RSSI value and the moving average of observedRSSI values are reflected over time from point 3720 to point 3725 andthen to point 3730. Master node 3410 identifies point 3730 as a thirdcheckpoint event because it detects another n number of successivesignals since the second checkpoint event at point 3720. As such, masternode 3410 identifies point 3730 as a third checkpoint event, which maybe reported to server 3400 as a type of event candidate.

In FIG. 37D, master node 3410 may help conserve onboard memory 415/420by deleting from the event data 3500 the intervening actual observedRSSI values and the moving averages between the prior two checkpointevents. Doing so allows the master node 3410 to more efficiently useit's onboard resources and focus on maintaining the summarizedinformation about the observed parameter of the detected successiveadvertising signals (e.g., the observed RSSI values as smoothed by themoving average processing).

Master node 3410 may then continue to scan/monitor for more successivelydetected signals and identify point 3740 in FIG. 37E as a fourthcheckpoint event, which may be reported to server 3400 as a type ofevent candidate before reducing what master node 3410 maintains inmemory as event data 3500 as shown in FIG. 37F.

An embodiment of master node 3410 may identify a type of event candidateby, for example, identifying a pattern between the detected advertisingsignals. For example, master node 3410 may observe a change in theobserved parameter of the advertising signals—e.g., a pattern showingthat the observed RSSI values are dropping. FIG. 37G illustratesadditional detections of successive signals where the pattern observedreflects shift in observed RSSI value between points 3740 to 3741 to3743. In particular, as master node 3410 determines the moving averageof the sample window as points 3741 and 3743 appear within the samplewindow, master node 3410 generates moving averages of the observed RSSIvalues reflected in points 3740 and 3745. With those moving averagesthat have changed over time, as shown in FIG. 37G, a detected shiftbetween the observed moving averages between point 3740 (the most recentcheckpoint) and point 3745 (the most recently determined moving averageof observed RSSI values) is shown as ΔRSSI. As time proceeds and furthersuccessive advertising signals are detected by master node 3410, thedetected shift between the most current average of observed RSSI valuesand the average for the most recent checkpoint (i.e., ΔRSSI) may becompared to a threshold value to see if the detected shift issignificant enough to report to the server 3400. In other words, asshown in FIG. 37H, when ΔRSSI is greater than RSSI_(threshold) at point3755, master node 3410 identifies point 3755 as a shift event, which maybe reported to server 3400 as a type of event candidate before reducingwhat master node 3410 maintains in memory as event data 3500 as shown inFIG. 37I.

FIGS. 37J-37M illustrate further detections of successive advertisingsignals from ID node 120 a as the observed RSSI values (and notablytheir respective moving averages) level off before dropping down to apoint 3775 after which no further successive advertising signal from IDnode 120 a is detected before the gap time elapses. In other words,master node 3410 may then continue to scan/monitor for more successivelydetected signals as shown in FIGS. 37J-37M; identify points 3750 and3765 in FIG. 37J as a fifth and sixth checkpoint event, respectively;may report the fifth and sixth checkpoint events in due course to server3400 as a types of event candidate before reducing what master node 3410maintains in memory as event data 3500 as shown in FIGS. 37K and 37L;and then identifies point 3775 as an offline event, which may bereported to server 3400 as a type of event candidate before reducingwhat master node 3410 maintains in memory as event data 3500 as shown inFIG. 37M.

In summary, the graphs of FIGS. 37A-37M represent embodiments of anexemplary event horizon where events related to an ID node may bedetected, identified, monitored, and reported to server 3400. Thisparticular example, the series of successively detected advertisingsignals are received by the master node 3410 from the first sightedadvertising signal detected at point 3700 and through the last sightedadvertising signal master node detected at point 3775 as long as the gaptime between successive ones of the detected signals has not elapsed(I., the time between successive detected signals is less than athreshold time).

However, in some instances, the particular ID node may only briefly comewithin range of master node 3410, and master node 3410 may be able todetect only one or just a few successive advertising signals broadcastby the ID node, and then lose further contact with the ID node. Thus,while the example shown in FIGS. 37A-37M has master node 3410 initiallydetecting enough signals from the ID node over time to identify anonline event, in other examples, the gap time between successive ones ofthe detected advertising signals may elapse prior to the online event.In such a situation, master node 3410 may identify the point of timewhere the gap time elapsed after the first sighting as a spurious eventrelated to the ID node, which may then be reported to server 3400 asstill another type of event candidate.

Those skilled in the art will appreciate that such a general example ofan embodiment that monitors for an event candidate based at least upon acomparison of observed parameters (e.g., timing and/or observed signalstrength levels) of different detected signals may be extended tomonitor one or more different ID nodes and report event candidateinformation to server 3400 about the different monitored ID nodes in asimplified and summarized manner. Server 3400 may then be able to learnfrom such reported event candidates (e.g., related to just one ID nodeand/or from a combination of reported event candidates related tomultiple ID nodes). Thus, the various different embodiments describedherein are applicable to a larger scale monitoring system deployedwithin and as part of an exemplary wireless node network that may alsohave different master nodes reporting their respective event candidatesto the same server rather than just a single master node and wheredifferent master nodes may report different event candidates that arerelated to the same ID node. In such a manner, the server 3400 may beprovided with different perspectives on the observed status of oneparticular ID node as provided by multiple master nodes that may bewithin a range of the particular ID node.

Those skilled in the art will also appreciate that other examples of anembodiment may use the detected advertising signals in accumulatedgroups or sets that are represented internal to the master node 3410 asa checkpoint or checkpoint summary. The comparison of checkpoints mayindicate a node event of such significance to warrant reporting as anevent candidate to the server 3400. Thus, the insight provided by themonitoring master node 3410 may be based upon simply two detectedadvertising signals or, in other instances, involve generating internalrepresentations of groups of the advertising signals so as to manage howfrequently the master node 3410 compares the observed parameters (e.g.,RSSI values) to identify a node event that warrants reporting to server3400 as an event candidate.

In light of the discussion above related to the exemplary system shownin FIG. 34, the exemplary master node 3410 shown in FIG. 35, theexemplary server 3400 shown in FIG. 36, and the exemplary operationalexplanation provided in conjunction with FIGS. 37A-37M, what follows aredescriptions of further embodiments of methods, apparatus, and systemsfor enhanced monitoring for an event candidate within a wireless nodenetwork.

In more detail, FIG. 38 is a flow diagram illustrating an exemplarymethod for monitoring for an event candidate within a wireless nodenetwork based upon receipt of a first and second advertising signalbroadcast by an ID node in accordance with an embodiment of theinvention. In this method embodiment, the wireless node networkcomprises at least a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node. Referring now to FIG. 38, method 3800 begins with themaster node receiving a first advertising signal broadcast by a first ofthe ID nodes at step 3805 and then receiving a second advertising signalbroadcast by the first ID node at step 3810 after the first ID nodebroadcasts the first advertising signal. At step 3815, method 3800proceeds with the master node identifying the event candidate based upona comparison of an observed parameter of the first advertising signaland the second advertising signal. Once the event candidate isidentified in step 3815, method proceeds to step 3820 where the masternode reports the event candidate to the server. Such reporting, in afurther embodiment, may have the master node simplifying a data feedabout the first ID node by sending the event candidate to the server assummary information reflecting an observed change between the firstadvertising signal and the second advertising signal. In other words, anembodiment of step 3820 may have the event candidate reported to theserver as a way to avoid the need to update the server with informationon all signals received by the master node from the first ID node.

In further embodiments of method 3800, identifying the event candidatemay be accomplished with an increased level of detail. For example, inone further embodiment, identifying the event candidate at step 3815 mayhave the master node identifying a pattern between at least the firstadvertising signal and the second advertising signal based upon theobserved parameter. The identified pattern, such as an identifieddecreasing observer signal strength level pattern (similar to that shownin FIGS. 37G and 37H), may reflect summarized information related to thefirst ID node as the event candidate. In more detail, identifying theevent candidate at step 3815 may involve identifying an observed patternbetween at least a first signal strength value of the first advertisingsignal and a second signal strength value of the second advertisingsignal, where the observed pattern reflects summarized informationrelated to the first ID node as the event candidate.

In other embodiments of method 3800, identifying the event candidate mayinvolve a moving average of what may be observed. In more detail,identifying the event candidate at step 3815 may have the master nodecomparing the observed parameter of the second advertising signal to anaverage of the observed parameters of a set of prior advertising signalsfrom the first ID node including the first advertising signal. Forexample, as discussed above with reference to FIGS. 37A-37M, a movingaverage of observed RSSI values may be determined and used to identifythe event candidate where the moving average spans a set of n detectedadvertising signals that span a sample window.

In still further embodiments of method 3800, the observed parameter thatis the focus of comparing different monitored and detected ID nodeadvertising signals in step 3815 may be further implemented in variousforms and combinations as part of identifying the event candidate. Inmore detail, the observed parameter in one embodiment may comprise areceived signal strength indicator (RSSI) reflecting a signal strengthas detected by the master node. As such, the step of identifying theevent candidate at step 3815 may comprise comparing a received signalstrength indicator value of the second advertising signal to an averageof a set of received signal strength indicator values of advertisingsignals from the first ID node broadcast prior to the second advertisingsignal. In still more detail, the averaged set of received signalstrength indicator values of advertising signals from the first ID nodebroadcast prior to the second advertising signal in a further embodimentmay comprise a moving average of the set of received signal strengthindicator values of advertising signals from the first ID node broadcastwithin a moving window prior to the second advertising signal. Forexample, as described above, a moving average may involve a samplewindow of n detected successive advertising signals where the detectedsuccessive signals are serially detected prior to a gap time elapsingbetween each of the detected signals.

In more embodiments of method 3800, the observed parameter may involvedetecting a shift in what is observed by the master node as the receivedsignal strength value of the monitored advertising ID node signals. Inother words, the observed parameter in one embodiment may comprise ashift in the observed signal strength value as received by the masternode. As such, identifying the event candidate at step 3815 may furthercomprise detecting the shift in received signal strength value whencomparing the first advertising signal and the second advertisingsignal, and identifying the event candidate as a shift event when thedetected shift in received signal strength value is at least a thresholdvalue.

In some embodiments, the master node may wait to observe a more completeshift in the observed signal strength value before reporting therelevant event candidate to the server. In particular, a furtherembodiment may have the observed parameter comprising an observed shiftin the signal strength value as received by the master node. As such,the step of identifying the event candidate at step 3815 and reportingthe event candidate to the server at step 3820 may further comprise moredetailed steps in a further embodiment.

For example, such detailed steps may comprise detecting a beginningshift in received signal strength value when the observed shift in thesignal strength value between the received first advertising signalcompared to the received second advertising signal is at least aninitiating threshold value; the master node receiving a subsequentadvertising signal broadcast by the first ID node after the first IDnode broadcasts the second advertising signal; detecting a continuedshift in received signal strength value when the observed shift in thesignal strength value between the received second advertising signalcompared to the received subsequent advertising signal; and thenreporting the event candidate by the master node to the server as ashift event only after detecting the beginning shift and if the detectedcontinued shift is less than a continued event threshold value. In thisway, the master node may further enhance simplification of the data feedto the server. In other words, an embodiment may have the reporting stepdelaying transmission of the event candidate to the server by the masternode until the detected continued shift based upon the observed signalstrength value of the subsequent advertising signal is less than thecontinued event threshold value.

In another embodiment, rather than waiting to report the shift event,the master node may first report the shift event as the event candidateafter detecting the first threshold (e.g., the initiating thresholdvalue as explained above). Thereafter, if the master node detects afurther drop or change in received signal strength value beyond anotherthreshold, the master node may report another shift event as the eventcandidate. Otherwise, the master node may smooth out shift eventsbetween the first and final checkpoint within a continuous multi-pointshift event.

In still further embodiments, the observed parameter in method 3800 mayinvolve timing between successive detected advertising signals. In moredetail, the observed parameter in an embodiment may comprise a detectedtime between successive advertising signals broadcast from the first IDnode and as received by the master node. As such, the step ofidentifying the event candidate at step 3815 may comprise detecting atime gap between the first advertising signal and the second advertisingsignal as the observed parameter (e.g., using the clock/timer 460 onmaster node 3410) and identifying the event candidate when the detectedtime gap is less than a threshold time gap.

Additionally, still further embodiments of method 3800 may identify theevent candidate with more specificity as being a particular type ofevent. In more detail, in a further embodiment, identifying the eventcandidate at step 3815 may have the master node identifying the eventcandidate as an online event when the detected time gap is less than thethreshold time gap and the master node receives at least one additionaladvertising signal broadcast by the first ID node within the thresholdtime gap after the second advertising signal. In still more detail,identifying the event candidate as the online event may occur when both(a) the detected time gap between the first advertising signal and thesecond advertising signal is less than the threshold time gap and (b)the master node has received at least a threshold number of advertisingsignals from the first ID node each of which are received by the masternode within the threshold time gap from each other, where receipt of thefirst advertising signal and receipt of the second advertising signalare included in the threshold number of advertising signals receivedfrom the first ID node. For example, an online event is identified bymaster node 3410 with reference to point 3710 shown in FIG. 37A andtiming between the successively detected signals after point 3700 (whichare each within the threshold time gap which, if elapsed, would indicatethe initial detection was more of a spurious or sporadic type of event).

In another further embodiment of method 3800, step 3815 may have themaster node identifying the event candidate as an offline event whenboth (a) the detected time since the master node received the secondadvertising signal is greater than a threshold time gap and (b) themaster node previously identified an online event related to signalsfrom the first ID node including the first advertising signal and thesecond advertising signal. Such an example of identifying an offlineevent is reflected in the graph of FIG. 37K at point 3775 where anonline event was identified by master node 3410 at 3710 and the timeafter the master node 3410 received the signal associated with point3775 has elapsed past a threshold time gap as ID node 120 a may nolonger be broadcasting or may no longer be within range of master node3410 and, thus, is considered offline relative to master node 3410.

In still another embodiment of method 3800, step 3815 may have themaster node identifying the event candidate as a sporadic event when themaster node receives at least the first advertising signal and thesecond advertising signal but does not receive at least a thresholdnumber of advertising signals from the first ID node within a definedperiod of time from when the master node receives the first advertisingsignal.

Still further embodiments may have step 3815 identifying the eventcandidate as a checkpoint event when a periodic reporting interval endsand based upon the comparison of the observed parameter of the firstadvertising signal and the second advertising signal. For example, asshown in FIG. 37B, master node 3410 identifies point 3720 as being acheckpoint event after the reporting interval between point 3710 andpoint 3720 ends and the comparison at point 3720 involves a movingaverage of the observed RSSI values over the sample window.

Method 3800 may also identify other event candidates based on changes inthe observed parameter of the detected signals when the observedparameter is a type of data in the detected signals. Examples of suchother types of node events may include a profile change event, atransmission power change event, and an environmental change event. Inmore detail, an embodiment may have method 3800 further implement step3815 with the observed parameter comprising an observed profile setting,and with the master node identifying the event candidate as a profilechange event when the comparison indicates the observed profile settingof the second advertising signal is different than the observed profilesetting of the first advertising signal. Such an observed profilesettings may generally relate to operation of the first ID node and/oroperation of the master node. A more detailed example may have anexemplary observed profile setting taking the form of an observedresource parameter (e.g., a parameter indicating current memory usage bythe node, current free memory in the node, present battery liferemaining for the node, and the like for onboard node resources) asindicated in a header of an advertising signals from the first node.Thus, a change to an observed resource parameters may be considered as atype of change to an observed profile setting in advertising signalsover time. In summary, the observed parameters underlying identificationof the event candidate may involve detected changes to how a nodespecifically indicates it is operating according to an operationalprofile for the node.

In a similar fashion, another embodiment may have method 3800 furtherimplement step 3815 with the observed parameter comprising an outputpower setting for the first ID node, and with the master nodeidentifying the event candidate as a transmission power change eventwhen the comparison indicates the observed output power setting relatedto the second advertising signal is different than the observed outputpower setting related to the first advertising signal. Thus, thoseskilled in the art will appreciated that an observed parameter of anoutput power setting for the first ID node is a setting from theperspective of the broadcaster (e.g., first ID node), in contrast to anobserved signal strength value that is a measurement of from theperspective of the receiver (e.g., the master node). In other words,while FIGS. 37A-37M are illustrated with an observed parameter ofsignals detected by master node 3410 to the observed RSSI value of theadvertising signal, other embodiments may have the master node 3410observing and monitoring an output power setting of the advertisingsignal (which is a power from the perspective of the broadcaster, incontrast to the observed RSSI value that is a power from the perspectiveof the receiver) to identify the event candidate as a transmission powerchange event.

Additionally, still another embodiment may have method 3800 furtherimplement step 3815 with the observed parameter comprising sensor datagathered by a sensor on the first ID node, and with the master nodeidentifying the event candidate as an environmental change event whenthe comparison indicates a second sensor data value included as part ofthe second advertising signal is different than a first sensor datavalue included as part of the first advertising signal. In more detail,the master node may identify the event candidate as an environmentalchange event when the comparison indicates a second sensor data valueincluded as part of the second advertising signal reflects a departurefrom a first sensor data value included as part of the first advertisingsignal, where the departure is more than a threshold difference. Thus,detected changes in environmental related sensor data as included inparts of the detected advertising signals may cause the master node toidentify a type of event candidate.

Further embodiments of method 3800 may include further steps that maychange how quickly the master node reports event candidates to theserver. For example, method 3800 may further have the master nodedetecting an alert flag from the first ID node, where the alert flag ispart of at least one of the first advertising signal and the secondadvertising signal. Such an alert flag may, for example, be a part of anadvertising packet signal header that indicates an alert stage status aspreviously explained relative to advertising data and flags (such asstatus flags) that may be used in advertising packets. Upon detectingthe alert flag, the master node may then alter the reporting intervalfor how frequently the master node may send updates or report eventcandidates (e.g., how long before the next checkpoint event wheresummarized information on the node is reported to the server). Forexample, the periodic reporting interval may be reduced when the masternode detects the alert flag. Such a reporting interval may be a anadjustable value, such as a time period adjustable by the master node ora number of signal receptions adjustable by the master node beforereporting further event candidates (e.g., new checkpoint events, and thelike). In such an embodiment, the master node may be able to adaptivelyrecognize that an ID node may have an alert status that, once detected,may desirably be handled more quickly or with more frequent updates backto the server so that the server may more efficiently and effectivelymanage the alert status situation with management feedback to the masternode and other control input.

Another embodiment may implement an alert flag as a profile identifiercorresponding to one of many different types of operational profiles(such as alert profiles) used with different ID nodes. In thisembodiment, upon detecting the profile identifier, the master node maythen alter certain monitoring functionality given the master node hasbeen made aware of a particular alert profile being used by theparticular ID node without the need to burden the backend server forsuch information. The embodiment may have the monitoring master node,such as master node 3410, maintain each of the different types of alertprofiles for the different types of ID nodes as part of profile data430. With the profile identifier, the master node is able to adapt howit monitors this particular ID node. More specifically, the profileidentifier informs the master node which of the alert profiles are beingused and how to adapt monitoring and reporting about the particular IDnode, such as via node management rules related to the time intervalsand threshold values (such as a reporting interval, threshold time gaps,a threshold number of advertising signals to receive from an ID nodethat corresponds to an online event, and the like). This allows the IDnode to autonomously or responsively change to an alert profile,generate new advertising signals where the new signals include theappropriate profile identifier within a header of the signals after thechange to the alert profile, which then allows the monitoring masternode to learn of this alert profile usage and adapt how the master nodemonitors this particular ID node and reports about the ID nodeaccordingly. As such, the master node monitoring the particular ID nodein this embodiment is spared the need to burden the backend server.

In a further embodiment, however, the backend server may initiate achange of alert profile and, in some cases, may create a new alertprofile for use by certain ID nodes. For example, backend server 3400may create the new alert profile as part of profile data 530 on server3400 (as shown in FIG. 36). Server 3400 may then push or otherwisetransmit the new alert profile to relevant managing nodes (such asmaster node 3410) that manage and monitor those particular ID nodes.Such managing nodes may then store the new alert profile (having new orupdated management rule data) and a corresponding profile identifier inprofile data 430 in memory onboard the master node. The managing node(e.g., master node 3410) may then provide the new alert profile and thecorresponding profile identifier to the particular ID nodes as a type ofupdated node management rule to be used by the ID node. In this way, theID node can be updated to autonomously or selectively operate in a newmanner according to the new alert profile and in a way that can beefficiently recognized by the monitoring master node.

Method 3800 may also, in some embodiments, have the master node resetinformation collected based upon the first advertising signal and thesecond advertising signal after reporting the checkpoint event to theserver by the master node for data reduction purposes on the masternode. For example, as explained with reference to FIG. 37D, master node3410 may help conserve onboard memory 415/420 by deleting from the eventdata 3500 the intervening actual observed RSSI values and the movingaverages between the prior two checkpoint events. Deleting such data isa way of resetting the information collected (e.g., data on the observedvalues and timing related to certain of the detected advertisingsignals) by master node 3410. Doing so allows the master node 3410 tofocus on maintaining the summarized information about the observedparameter of the detected successive advertising signals and reduce whatis maintained for data reduction and simplification purposes.

Method 3800 may also, in further embodiments, have the master nodereceiving and reacting to server feedback related to reported eventcandidates. For example, another embodiment of method 3800 may also havethe master node receiving an adjustment response from the server basedupon the event candidate. In more detail, the adjustment response maycomprise an adjusted profile for at least one of the master node and thefirst ID node or an adjusted profile for at least one of the other IDnodes. The adjustment response may also comprise, in some embodiments,updated context data reflecting the reported event candidate.

Another embodiment of method 3800 may extend to generating and comparingcheckpoints as part of identifying the event candidate. In particular,method 3800 may also have the master node receive a third advertisingsignal broadcast by the first ID node after the first ID node broadcaststhe second advertising signal, and then receive a fourth advertisingsignal broadcast by the first ID node after the first ID node broadcaststhe third advertising signal. The master node may then generate a firstcheckpoint summary as a statistical representation of the firstadvertising signal and the second advertising signal (e.g., a mean, amedian, an average, a moving average, or a weighted average). Similarly,the master node may generate a second checkpoint summary as astatistical representation of the third advertising signal and thefourth advertising signal. Based upon these two checkpoints thatstatistically summarize relevant advertising signals, the master nodemay identify the event candidate. In other words, the master node mayidentify the event candidate based upon a comparison of an observedparameter for each of the first checkpoint summary and the secondcheckpoint summary (such as a comparison of average observed signalstrength for the first checkpoint summary and the second checkpointsummary).

Those skilled in the art will appreciate that method 3800 as disclosedand explained above in various embodiments may be implemented on anexemplary master node (e.g., exemplary master node 3410 in FIG. 35)running one or more parts of the master control and management code 425in conjunction with event detection engine code 3415 to perform steps ofmethod 3800 as described above. Such code may be stored on anon-transitory computer-readable medium, such as memory storage 415 onmaster node 3410. Thus, when executing such code, the master node may bespecially adapted to interact with other network devices (such as one ormore ID nodes as shown in FIG. 34 and server 3400 as shown in FIG. 34)as the master node's processing unit 400 is specially adapted to beoperative to perform algorithmic operations or steps from the exemplarymethods disclosed above, including method 3800 and variations of thatmethod.

FIG. 39 is a flow diagram illustrating another exemplary method formonitoring for an event candidate within a wireless node network basedupon detection or receipt of a plurality of advertising signalsbroadcast by an ID node over time in accordance with an embodiment ofthe invention. In this method embodiment, the wireless node networkcomprises network components at three different levels of the networkincluding at least a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node. Referring now to FIG. 39, method 3900 begins at step 3905with the master node detecting a plurality of advertising signalsbroadcast by a first of the ID nodes over a time period. In more detail,the plurality of advertising signals may be successively detectedadvertising packet signals that were broadcast over the time period bythe first ID node.

At step 3910, method 3900 proceeds with the master node identifying theevent candidate relative to the first ID node when an observed parameterof the advertising signals changes over the time period to reflect theevent candidate. As with method 3800, various further embodiments ofmethod 3900 may implement step 3910 with an increased level of detail,as discussed further below. At step 3915, method 3900 concludes with themaster node reporting the event candidate to the server. In more detail,an embodiment may have the master node reducing data obtained by themaster node about the first ID node (e.g., through observed parametersof detected advertising signals broadcast by the first ID node) bysending the event candidate to the server as summary informationreflecting an observed change between advertising signals.

As noted above, further embodiments of method 3900 may have the masternode identifying the event candidate with more details steps. Forexample, in one further embodiment, identifying the event candidate atstep 3910 may have the master node identifying the event candidate basedon an observed parameter that comprises a summarized observed patternbetween the advertising signals. For example, the observed parameter maycomprise an observed signal strength value (such as a received RSSIvalue) as detected by the master node. In such an embodiment, reportingthe event candidate to the server may avoid the need to update theserver with too much information about the signal strength value of eachof the advertising signals received by the master node from the first IDnode.

In other embodiments of method 3900, identifying the event candidate mayinvolve a moving average of what may be observed by the master node. Inmore detail, identifying the event candidate at step 3910 may have themaster node comparing the observed parameter of a most recently detectedone of the advertising signals to a moving average of the observedparameter of the previously detected ones of the advertising signals toidentify the event candidate.

As with method 3800, further embodiments of method 3900 use a morespecific type of observed parameter in step 3910 when identifying theevent candidate. In one embodiment where the observed parametercomprises a received signal strength indicator (RSSI) reflecting asignal strength as detected by the master node, step 3910 of method 3900may have the master node comparing a received signal strength indicatorvalue of a most recently detected one of the advertising signals to amoving average of the received signal strength indicator values of theprior advertising signals within a prior moving window to identify theevent candidate.

In another embodiment of method 3900, the observed parameter may involvedetecting a shift in what is observed by the master node as the receivedsignal strength value of the advertising ID node signals. In otherwords, the observed parameter in one embodiment may comprise a shift insignal strength as detected by the master node. As such, the step ofidentifying the event candidate may have the master node identifying theevent candidate as a shift event when the detected shift in the signalstrength value for each of the advertising signals exceeds a thresholdvalue.

In a more detailed embodiment where the observed parameter comprises anobserved shift in the signal strength value as received by the masternode, the master node may implement steps 3910 and 3915 by detecting abeginning shift in received signal strength value when the observedshift in the signal strength value between the plurality of advertisingsignals is at least an initiating threshold value; having the masternode receive at least one subsequent advertising signal broadcast by thefirst ID node after the first ID node broadcasts the plurality ofadvertising signals; detecting a continued shift in received signalstrength value when the observed shift in the signal strength valuebetween a last of the received plurality of advertising signals comparedto the received subsequent advertising signal; and having the masternode reporting the event candidate to the server as a shift event onlyafter detecting the beginning shift and if the detected continued shiftis less than a continued event threshold value.

Additional embodiments may identify the event candidate as other typesof events. For example, in one embodiment of method 3900, the masternode may identify the event candidate as an online event in step 3910when the master node has received at least a threshold number of theadvertising signals from the first ID node within a threshold time gapbetween successive ones of the advertising signals. In anotherembodiment, the master node may identify the event candidate as anoffline event in step 3910 when (a) an elapsed time since the masternode received a last of the advertising signals is greater than athreshold time gap and (b) the master node previously identified anonline event related to at least a portion of the advertising signalsfrom the first ID node. In a further embodiment, the master node mayidentify the event candidate as a sporadic event in step 3910 when themaster node has received at least a first of the advertising signals butnot a threshold number of successive ones of the advertising signalswithin a defined period of time from when the master node receives thefirst advertising signal. In still another embodiment, the master nodemay identify the event candidate as a checkpoint event in step 3910 whenthe time period ends and the master node detects at least one additionaladvertising signals broadcast by the first ID node.

Method 3900 may also identify event candidates based on changes in theobserved parameter of the detected signals when the observed parameteris a type of data in the detected signals. For example, in a furtherembodiment of method 3900, the observed parameter may comprise anobserved profile setting associated with a node. As such, the step ofidentifying the event candidate in step 3910 may further involveidentifying the event candidate as a profile change event when theobserved profile setting of the advertising signals changes from a firstsetting to a second setting over the time period. Such an observedprofile setting may relate to operation of the first ID node and/or theoperation of the master node. In another example, the step ofidentifying the event candidate in step 3910 may further involveidentifying the event candidate as a transmission power change eventwhen the observed parameter comprises an observed output power settingfor the first ID node. In still another example, the step of identifyingthe event candidate in step 3910 may further involve identifying theevent candidate as an environmental change event when the observedparameter comprises sensor data gathered by a sensor on the first IDnode.

Further embodiments of method 3900 may include more steps that maychange how quickly the master node reports event candidates to theserver. For example, method 3900 may further have the master nodedetecting an alert flag from the first ID node, where the alert flag ispart of at least one of the plurality of advertising signals. Once themaster node detects the alert flag from at least one of the advertisingsignals (e.g., from header information in one or more of the advertisingsignals), the master node may reduce the time period after which themaster node identifies and reports the event candidate to the server.

Another embodiment of method 3900 may implement the alert flag as aprofile identifier corresponding to one of many different types ofoperational profiles (such as alert profiles) used with different IDnodes as explained above. In more detail, the profile identifierindicates a particular alert profile being used by the first ID node.Such an alert profile may be one of a plurality of operational profilesthat govern advertising signal broadcasting operations by the first IDnode.

In a further embodiment, however, the backend server may initiate achange of alert profile and, in some cases, may create a new alertprofile for use by certain ID nodes. For example, backend server 3400may create the new alert profile as part of profile data 530 on server3400 (as shown in FIG. 36). Server 3400 may then push or otherwisetransmit the new alert profile to relevant managing nodes (such asmaster node 3410) that manage and monitor those particular ID nodes.Thus, an extension of method 3900 may have the master node receiving anew alert profile and storing the new alert profile (having new orupdated management rule data) and a corresponding profile identifier inprofile data 430 in memory onboard the master node. The master node maythen provide the new alert profile and the corresponding profileidentifier to the first ID node, for example, as a type of updated nodemanagement rule to be used by the first ID node. In this way, the IDnode can be updated to autonomously or selectively operate in a newmanner according to the new alert profile and in a way that can beefficiently recognized by the monitoring master node.

An additional embodiment of method 3900 may also have the master noderesetting information collected by the master node based upon theadvertising signals after reporting the checkpoint event as the eventcandidate to the server to conserve use of memory on the master node.This is a way to simplify the data feed between the master node andserver as it relates to monitoring for event candidates and the serverstay abreast of the status of nodes within the network.

Method 3900 may also, in further embodiments, have the master nodereceiving and reacting to server feedback related to reported eventcandidates. For example, another embodiment of method 3900 may also havethe master node receiving an adjustment response from the server basedupon the event candidate, where the adjustment response may comprise anadjusted profile for at least one of the master node and the first IDnode. In a further embodiment, the adjustment response may comprise anadjusted profile for at least one of the other ID nodes and may compriseupdated context data reflecting the reported event candidate.

Another embodiment of method 3900 may extend to generating and comparingcheckpoints as part of identifying the event candidate. In particular,method 3900 may have the master node detecting a first set ofadvertising signals broadcast by the first ID node and a second set ofadvertising signals broadcast by the first ID node after the first setof advertising signals, where the first set of advertising signals andthe second set of advertising signals are part of the plurality ofadvertising signals detected in step 3905. This further embodiment ofmethod 3900 proceeds by having the master node generating a firstcheckpoint summary as a statistical representation of the first set ofadvertising signals and, similarly, generating a second checkpointsummary as a statistical representation of the second set of advertisingsignals. Based upon these two checkpoints that statistically summarizerelevant sets or groups of successive advertising signals, the masternode may identify the event candidate. In other words, the master nodemay identify the event candidate based upon a comparison of an observedparameter for each of the first checkpoint summary and the secondcheckpoint summary (such as a comparison of average observed signalstrength for the first checkpoint summary and the second checkpointsummary).

Those skilled in the art will appreciate that method 3900 as disclosedand explained above in various embodiments may be implemented on anexemplary master node (e.g., exemplary master node 3410 in FIG. 35)running one or more parts of the master control and management code 425in conjunction with event detection engine code 3415 to perform steps ofmethod 3900 as described above. Such code may be stored on anon-transitory computer-readable medium, such as memory storage 415 onmaster node 3410. Thus, when executing such code, the master node may bespecially adapted to interact with other network devices (such as one ormore ID nodes as shown in FIG. 34 and server 3400 as shown in FIG. 34)as the master node's processing unit 400 is specially adapted to beoperative to perform algorithmic operations or steps from the exemplarymethods disclosed above, including method 3900 and variations of thatmethod.

FIG. 40 is a flow diagram illustrating an exemplary method for enhancedmonitoring for an event candidate within a wireless node network basedupon receipt of a plurality of signals from an ID node and detecting aplurality of time gaps between suggestive ones of the signals inaccordance with an embodiment of the invention. In this methodembodiment, the wireless node network comprises at least a plurality ofID nodes, a master node in communication with the ID nodes, and a serverin communication with the master node. Referring now to FIG. 40, method4000 begins at step 4005 with the master node scanning for a first ofthe ID nodes. For example, an embodiment may have master node 3410 usinga Bluetooth® radio transceiver as part of short range communicationinterface 480 in a scanning mode to listen for Bluetooth® formattedadvertising packet signals being broadcast by nearby ID nodes. Method4000 has the master node receiving a plurality of signals from the firstID node as part of step 4010 and detecting a plurality of time gapsbetween successive ones of the signals as the master node receives eachof the signals as part of step 4015.

The observed signal levels of the detected signals and the detected timegaps are exemplary types of observed parameters used by method 4000 whenidentifying an event candidate. In particular, at step 4020, method 4000proceeds with the master node comparing each of the signals to identifya change in an observed parameter of each of the signals. In moredetail, the identified change in the observed parameter of the signalsmay comprise a detected shift between the signals based upon theobserved parameter over time. For example, such a shift may be when theobserved parameter is an observed signal strength value as detected bythe master node and the observed signal strength value over timeindicates a meaningful shift (such as when the detected shift exceeds athreshold difference in observed signal strength value as shown in theexample of FIG. 37H).

In still more detail, when a further embodiments has the observedparameter be a received signal strength indicator (RSSI) reflecting asignal strength as detected by the master node; and the comparing stepof step 4020 may comprise comparing a received signal strength indicatorvalue of a most recently received one of the signals to a moving averageof the received signal strength indicator values of a rolling window ofthe previously received ones of the signals to identify the eventcandidate.

At step 4025, method 4000 proceeds with the master node identifying theevent candidate when at least one of the identified change in theobserved parameter and the detected time gaps matches event criteriaassociated with a particular type of node status or event to be reportedto the server. In a further embodiment of step 4025, the identifiedevent candidate may be considered a shift event when the event criteriacomprises a condition met when (a) the master node identifies the changein the observed parameter of the signals over time as reflecting a shiftin the observed signal strength value for the signals over time and (b)the shift exceeds a threshold value. In another embodiment where theobserved parameter may be an observed shift in the signal strength valueas received by the master node, the master node may identify the eventcandidate and may report the event candidate to the server by detectinga beginning shift in received signal strength value when the observedshift in the signal strength value between the received plurality ofsignals is at least an initiating threshold value; receiving at leastone subsequent signal broadcast by the first ID node after the first IDnode broadcasts the received plurality of signals; detecting a continuedshift in received signal strength value when the observed shift in thesignal strength value between a last of the received plurality ofsignals compared to the received subsequent signal; and having themaster node report the event candidate to the server as a shift eventonly after detecting the beginning shift and if the detected continuedshift is less than a continued event threshold value.

In another embodiment of step 4025, the event candidate may beconsidered an online event when the event criteria comprises a conditionmet when (a) the master node has received at least a threshold number ofsuccessive ones of the signals from the first node and (b) the detectedtime gaps between the successive ones of the signals do not exceed athreshold time gap.

In an additional embodiment of step 4025, the event candidate may beconsidered an offline event when the event criteria comprises acondition met when (a) an elapsed time since the master node received alast of the signals is greater than a threshold time gap and (b) themaster node previously identified an online event related to the rest ofthe signals received by the master node from the first ID node.

In a further embodiment of step 4025, the event candidate may beconsidered a sporadic event when the event criteria comprises acondition met when the master node has received at least a first of thesignals but not a threshold number of successive ones of the signalswithin a defined period of time from when the master node detects thefirst signal.

In still another embodiment of step 4025, the event candidate may beconsidered a checkpoint event when the event criteria comprises acondition met when a periodic reporting interval ends and the masternode detects at least one additional signal broadcast by the first IDnode.

Finally, at step 4030, method 4000 proceeds with the master nodereporting the event candidate to the server. In more detail, thereporting in step 4030 may comprise reducing, by the master node, dataobtained by the master node about the first ID node from the pluralityof signals by sending the event candidate to the server as only summaryinformation reflecting the change in the parameter of the signals overtime (rather than all information gathered by the master node relativeto the signals received over time). In other words, reporting the eventcandidate to the server may help avoid the need to update the serverwith information about the signal strength value of each of the signalsreceived by the master node from the first ID node.

In further embodiments, method 4000 may also identify further types ofevent candidates related to a profile change event, a transmission powerchange event, or an environmental change event. In particular, method4000 may also comprise identifying a profile change event when themaster node detects a changed profile setting of the signals over time,and having the master node report the profile change event to theserver. Likewise, method 4000 may have the master node identifying atransmission power change event when the master node detects a changedtransmission power setting of the signals over time, and then reportingthe transmission power change event relative to the server. Method 4000may also have the master node identifying an environmental change eventwhen the master node detects a change in sensor data gathered from thefirst ID node via the signals over time, and then reporting theenvironmental change event to the server.

A further embodiment of method 4000 may also change the interval ofreporting event candidates to the server to, for example, keep theserver more abreast of relevant node events observed by the master node.In more detail, an embodiment of method 4000 may have the master nodedetecting an alert flag reflecting a status of the first ID node (wherethe alert flag is part of at least one of the received plurality ofsignals) and then reducing the periodic reporting interval afterdetecting the alert flag. The periodic reporting interval may, forexample, comprise a time period adjustable by the master node or anumber of signal receptions adjustable by the master node or acombination of both adjustable aspects that impact and adaptively changethe periodic reporting interval under the alert flag conditions.

Another embodiment of method 4000 may implement an alert flag as aprofile identifier corresponding to one of many different types ofoperational profiles (such as alert profiles) used with different IDnodes as explained above. In more detail, such a profile identifier mayindicate an alert profile being used by the first ID node. Such an alertprofile may be one of a plurality of operational profiles that governadvertising signal broadcasting operations by the first ID node.

In another embodiment, method 4000 may also comprise the step ofresetting information collected by the master node based upon thesignals after reporting a checkpoint event as the event candidate to theserver to conserve use of memory on the master node. In such anembodiment (similar to that shown in FIGS. 37E and 37F), some of thedata collected by master node 3410 prior to a checkpoint event may bereset so that the memory space can be reused (i.e., is no longer filledwith information to be retained).

In still another embodiment, method 4000 may have the master nodereceiving feedback from the server based upon the reported eventcandidate and generating an appropriate master node response. In moredetail, method 4000 may further comprise the step of receiving anadjustment response from the server based upon the event candidate. Suchan adjustment response may comprise an adjusted profile for at least oneof the master node and the first ID node, or an adjusted profile for atleast one of the other ID nodes, or a combination of such adjustedprofiles. Such an adjustment response, in another example, may compriseupdated context data reflecting the reported event candidate where theserver has “learned” more about the contextual environment of the nodesbased on the reported event candidate and provides the updated contextdata so that the master node can enhanced and improve management ofitself and/or the ID nodes within its control with the updated contextdata.

Another embodiment of method 4000 may extend to generating and comparingcheckpoints (based on the advertising signals) as part of identifyingthe event candidate. In particular, method 4000 may also have the masternode receiving a first set of advertising signals broadcast by the firstID node and a second set of advertising signals broadcast by the firstID node after the first set of advertising signals, where the first setof advertising signals and the second set of advertising signals arepart of the plurality of signals received by the master node from thefirst ID node. Method 4000 may then have the master node generate afirst checkpoint summary as a statistical representation of the firstset of advertising signals, and similarly generate a second checkpointsummary as a statistical representation of the second set of advertisingsignals. As such, the comparing step 4020 may be modified to comprisecomparing an observed parameter for each of the first checkpoint summaryand the second checkpoint summary to identify the change.

Those skilled in the art will appreciate that method 4000 as disclosedand explained above in various embodiments may be implemented on anexemplary master node (e.g., exemplary master node 3410 in FIG. 35)running one or more parts of the master control and management code 425in conjunction with event detection engine code 3415 to perform steps ofmethod 4000 as described above. Such code may be stored on anon-transitory computer-readable medium, such as memory storage 415 onmaster node 3410. Thus, when executing such code, the master node may bespecially adapted to interact with other network devices (such as one ormore ID nodes as shown in FIG. 34 and server 3400 as shown in FIG. 34)as the master node's processing unit 400 is specially adapted to beoperative to perform algorithmic operations or steps from the exemplarymethods disclosed above, including method 4000 and variations of thatmethod.

A further embodiment of an exemplary master node apparatus for enhancedmonitoring for an event candidate within a wireless node network havinga plurality of ID nodes and a server is described below that operatessimilar to that described above with reference to FIG. 40 and theembodiments of method 4000. In this embodiment, the master nodeapparatus generally comprises a node processing unit and a memorystorage coupled to and used by the node processing unit (e.g., a nodevolatile memory 420 and a node memory storage 415). The memory storagemaintains at least an embodiment of event detection engine code (such asevent detection engine code 3415). The node processing unit is alsocoupled to and used with the first communication interface and thesecond communication interface. In particular, the first communicationinterface (e.g., short range communication interface 480 on exemplarymaster node 3410) is operative to communicate with at least a first ofthe ID nodes over a first communication path. In contrast, the secondcommunication interface (e.g., medium/long range communication interface485 on exemplary master node 3410) is operative to communicate with theserver over a second communication path. In some embodiments, the firstand second communication paths may be the same but in other embodimentsthe first and second communication paths may be distinct.

The node processing unit (e.g., processing unit 400 of master node3410), when executing the event detection engine code maintained on thememory storage, is operative to perform specific functions or steps thatadapt the master node apparatus via specialized and novel functionality.In particular, the node processing unit, as adapted by such code, isoperative to detect, via the first communication interface, a firstadvertising signal broadcast by the first ID node over the firstcommunication path; detect, via the first communication interface, asecond advertising signal broadcast by the first ID node over the firstcommunication path after the first ID node broadcasts the firstadvertising signal; compare an observed parameter of each of the firstadvertising signal and the second advertising signal; identify the eventcandidate based upon the comparison of the observed parameter of each ofthe first advertising signal and the second advertising signal; andcause the second communication interface to report the identified eventcandidate to the server over the second communication path.

In a further embodiment of this master node apparatus, the secondcommunication interface may transmit a message to the server whenreporting the identified event candidate where the message reflects theidentified event candidate as reduced monitoring overhead for the firstID node on the second communication path. More specifically, the messagereflecting the identified event candidate may include summaryinformation reflecting an observed change between the first advertisingsignal and the second advertising signal, in contrast to allobservations made by the master node apparatus. In more detail, wherethe observed parameter may be a signal strength value as detected by thenode processing unit via the first communication interface, the observedchange may be a shift in observed signal strength value between at leasta first signal strength value of the first advertising signal and asecond signal strength value of the second advertising signal. As such,the observed change may reflect summarized information related to thefirst ID node as the event candidate.

A further embodiment of this master node apparatus may have the nodeprocessing unit being operative to compare the observed parameter of thesecond advertising signal to an average of the observed parameters of aset of prior advertising signals from the first ID node including thefirst advertising signal. Stated another way, in an embodiment where theobserved parameter comprises a received signal strength indicator asdetected by the node processing unit, the node processing unit maycompare the observed parameter of each of the first advertising signaland the second advertising signal by being further operative to comparea received signal strength indicator value of the second advertisingsignal to an average of a set of received signal strength indicatorvalues of prior advertising signals from the first ID node including thefirst advertising signal. In still another embodiment, the averaged setof received signal strength indicator values of advertising signals fromthe first ID node broadcast prior to the second advertising signal maybe implemented as a moving average of the set of received signalstrength indicator values of advertising signals from the first ID nodebroadcast within a window prior to the second advertising signal.

In another embodiment of this master node apparatus, the node processingunit may be operative to identify the event candidate by being furtheroperative to detect a shift in received signal strength value whencomparing the signal strength value of first advertising signal and thesignal strength value of the second advertising signal, and thenidentify the event candidate as a shift event when the detected shift inreceived signal strength value is at least a threshold value. A furtherdetailed embodiment may have the observed parameter being an observedshift in the signal strength value as detected by the node processingunit. As such, the node processing unit may be operative to identify theevent candidate and cause the second communication interface to reportthe event candidate to the server by being further operative to (a)detect a beginning shift in received signal strength value when theobserved shift in the signal strength value between the plurality ofadvertising signals is at least an initiating threshold value; (b)detect, via the first communication interface, at least one subsequentadvertising signal broadcast by the first ID node after the first IDnode broadcasts the second advertising signal; (c) detect, via the firstcommunication interface, a continued shift in received signal strengthvalue when the observed shift in the signal strength value between thesecond advertising signal compared to the received subsequentadvertising signal; and (d) cause the second communication interface toreport the event candidate to the server as a shift event only afterdetecting the beginning shift and if the detected continued shift isless than a continued event threshold value.

In still other embodiments, the observed parameter may comprise a timebetween successive advertising signals broadcast from the first ID nodeand as detected by the node processing unit via the first communicationinterface. As such, the node processing unit may be operative toidentify the event candidate by being further operative to detect a timegap between the first advertising signal and the second advertisingsignal and identify the event candidate when the detected time gap isless than a threshold time gap.

Various further embodiments of this master node apparatus may bedescribed with more details on identifying the event candidate as aparticular type of node event. For example, in one embodiment, the nodeprocessing unit may be operative to identify the event candidate as anonline event when the detected time gap is less than the threshold timegap and the first communication interface detects at least oneadditional advertising signal broadcast by the first ID node within thethreshold time gap after the second advertising signal. In more detail,the node processing unit may be operative to identify the eventcandidate as the online event when (a) the detected time gap between thefirst advertising signal and the second advertising signal is less thanthe threshold time gap and (b) the first communication interface hasdetected at least a threshold number of advertising signals from thefirst ID node each of which are detected by the first communicationinterface within the threshold time gap from each other, where detectionof the first advertising signal and detection of the second advertisingsignal are included in the threshold number of advertising signals fromthe first ID node.

In another embodiment, the node processing unit may be operative toidentify the event candidate as an offline event when (a) the detectedtime since the first communication interface detected the secondadvertising signal is greater than a threshold time gap and (b) the nodeprocessing unit previously identified an online event related to signalsfrom the first ID node including the first advertising signal and thesecond advertising signal.

In still a different embodiment, the node processing unit may beoperative to identify the event candidate as a sporadic event when thefirst communication interface detects at least the first advertisingsignal and the second advertising signal but does not detect at least athreshold number of advertising signals from the first ID node within adefined period of time from when the first communication interfacedetects the first advertising signal.

In yet another embodiment, the node processing unit may be operative toidentify the event candidate as a checkpoint event when a periodicreporting interval ends and based upon the comparison of the observedparameter of the first advertising signal and the second advertisingsignal.

When the observed parameter comprises an observed profile setting, thenode processing unit may operative to identify the event candidate as aprofile change event when the comparison indicates the observed profilesetting of the second advertising signal is different than the observedprofile setting of the first advertising signal. In a similar manner,when the observed parameter comprises an observed output power settingfor the first ID node, the node processing unit may be operative toidentify the event candidate as a transmission power change event whenthe comparison by the node processing unit indicates the observed outputpower setting related to the second advertising signal is different thanthe observed output power setting related to the first advertisingsignal. And finally, when the observed parameter comprises sensor datagathered by a sensor on the first ID node, the node processing unit maybe operative to identify the event candidate as an environmental changeevent when the comparison by the node processing unit indicates a secondsensor data value included as part of the second advertising signaldiffers more than a threshold amount when compared to a first sensordata value included as part of the first advertising signal.

An embodiment of this master node apparatus may allow for adaptivechanging the interval of reporting an event candidate to the server inorder to respond, for example, to an alert situation. For instance, thenode processing unit may be further operative to detect an alert flagfrom the first ID node and reduce the periodic reporting interval upondetecting the alert flag. The alert flag may be part of a header for atleast one of the first advertising signal and the second advertisingsignal. And the periodic reporting interval may be a time periodadjustable by the node processing unit or a number of signal receptionsadjustable by the node processing unit.

A further embodiment of the master node apparatus may implement such analert flag as a profile identifier corresponding to one of manydifferent types of operational profiles (such as alert profiles) usedwith different ID nodes as previously explained. As such, the alert flagmay comprise a profile identifier indicating an alert profile being usedby the first ID node, where the alert profile is one of a plurality ofoperational profiles that governs advertising signal broadcastingoperations by the first ID node.

The node processing unit may also be operative to delete certain of thegathered signal information (e.g., observed signal strength values andtiming information collected from at least the first advertising signaland from the second advertising signal) stored on the memory storageafter causing the second communication interface to report thecheckpoint event to the server as part of reducing data that may be keptwhen monitoring for further event candidates.

As for responsive action that may be taken after reporting the eventcandidate, the node processing unit may be further operative to receive,via the second communication interface, an adjustment response from theserver based upon the event candidate reported. The adjustment responsemay comprise an adjusted profile for at least one of the master nodeapparatus and the first ID node or an adjusted profile for at least oneof the other ID nodes. In another embodiment, the adjustment responsemay include updated context data reflecting the reported eventcandidate, where such updated context data may be used by the nodeprocessing unit when managing the ID nodes.

Another embodiment of this master node apparatus may identify the eventcandidate from a checkpoint summary perspective of monitoringadvertising signals. In particular, such an embodiment may have the nodeprocessing unit of the master node apparatus being operative to detect,via the first communication interface, a third advertising signalbroadcast by the first ID node over the first communication path afterthe first ID node broadcasts the second advertising signal and thendetect, via the first communication interface, a fourth advertisingsignal broadcast by the first ID node over the first communication pathafter the first ID node broadcasts the third advertising signal. Thenode processing unit may also be operative to generate a firstcheckpoint summary as a statistical representation of the firstadvertising signal and the second advertising signal, and also generatea second checkpoint summary as a statistical representation of the thirdadvertising signal and the fourth advertising signal. The nodeprocessing unit may further be operative to compare the observedparameter for each of the first checkpoint summary and the secondcheckpoint summary, and then identify the event candidate based upon thecomparison of the observed parameter for each of the first checkpointsummary and the second checkpoint summary.

As generally explained with reference to FIG. 34, still anotherembodiment may include a monitoring system that identifies an eventcandidate within a wireless node network. The monitoring systemcomprises at least a server, an ID node broadcasting advertisingsignals, and a master node disposed within the wireless node network.The master node in this exemplary monitoring system may be implementedwith embodiments of the master node apparatus as set forth above.

In some situations, an exemplary ID node may be operating under aprofile that has it cycling power in accordance with rules defined inthe profile. As such, a master node observing the cycling ID node mayuse an altered method for monitoring for an event candidate given the IDnode is known or detected to be broadcasting with a cycling broadcast RFpower profile setting. FIG. 41 is a flow diagram illustrating anexemplary method for enhanced monitoring for an event candidate within awireless node network based upon receipt of a plurality of signals froman ID node and detecting if the ID node is broadcasting with a cyclingbroadcast RF power profile setting in accordance with an embodiment ofthe invention. Referring now to FIG. 41, method 4100 begins with thewireless node network having a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node. At step 4105, the master node receives a first plurality ofadvertising signals broadcast by a first of the ID nodes. Method 4100then proceeds to step 4110 where the master node detects if the first IDnode is broadcasting with a cycling broadcast RF power profile settingbased upon at least one of the first plurality of advertising signals.For example, the master node may look to a particular part of a headerof the advertising signal data packet being broadcast by the first IDnode to find a power profile. The power profile may indicate that thefirst ID node is currently operating in a mode under a cycling broadcastRF power profile setting that periodically has the ID node changing itsbroadcast power. If so, monitoring for an event candidate by the masternode may involve particular steps that may differ from monitoring for anevent candidate with ID nodes not operating under a cycling broadcast RFpower profile setting.

At step 4115, method 4100 proceeds with the master node receiving asecond plurality of advertising signals broadcast by the first ID nodeafter the first ID node broadcasts the first plurality of advertisingsignals. Such a second plurality of advertising signals is broadcastwith the cycling broadcast RF power profile setting (e.g., cycling froma low-power level, to a mid-power level, to a high power level). Thecycling broadcast RF power profile setting defines a cycle period overwhich the first ID node alters how it broadcasts at different powerlevels.

At step 4120, the master node determines a first average of an observedparameter for the first plurality of advertising signals within a firstwindow of time commensurate with the cycle period and then, at step4125, determines a second average of the observed parameter for thesecond plurality of advertising signals within a second window of timecommensurate with the cycle period. Determining such averages for theraw observed parameters (e.g., an observed signal strength value or RSSIvalue) over such a cycle period advantageously allows for a moremeaningful comparison in step 4130. In particular, step 4130 has themaster node identifying the event candidate when a comparison of thefirst average and the second average indicates an observed changerelative to the first ID node (such as when the second average observedsignal strength is more than a threshold less than or more than thefirst average observed signal strength). Thereafter, step 4135 has themaster node reporting the event candidate to the server.

Those skilled in the art will appreciate that method 4100 as disclosedand explained above in various embodiments may be implemented on anexemplary master node (e.g., exemplary master node 3410 in FIG. 35)running one or more parts of the master control and management code 425in conjunction with event detection engine code 3415 to perform steps ofmethod 4100 as described above. Such code may be stored on anon-transitory computer-readable medium, such as memory storage 415 onmaster node 3410. Thus, when executing such code, the master node may bespecially adapted to interact with other network devices (such as one ormore ID nodes as shown in FIG. 34 and server 3400 as shown in FIG. 34)as the master node's processing unit 400 is specially adapted to beoperative to perform algorithmic operations or steps from the exemplarymethods disclosed above, including method 4100 and variations of thatmethod.

More detailed embodiments that monitor for an event candidate mayinvolve further enhancements related to use of benchmark checkpoints andspecific types of event data generated that are provided as part of thereported event candidate to the server. A benchmark checkpoint event isgenerally a periodic point during an event horizon (should monitoringarrive upon at least an online event type of event candidate) thatsummarizes a number of observations of the master node (whether the rawobservations or a statistical representation of the observations (like amoving average)) since a prior benchmark checkpoint event. For example,a moving average of observed parameters (e.g., RSSI values as shown inFIGS. 37A-M) for detected advertising signals may rely upon a number, n,of successive advertising signals that define a window for the movingaverage. As such, the window essentially has of sample width n points intime where advertising signals are detected and from which to computethe moving average. As time proceeds and further successive advertisingsignals are detected, the moving average window of width n essentiallyslides forward in time to then only cover the last n advertising signalobservations. Thus, a first checkpoint event may be identified when themaster node has received a sufficient number of successive advertisingsignals from an ID node to fill the moving average window. Such a firstcheckpoint event based on the first moving average calculated in an IDnode's monitored event horizon may be considered a first benchmarkcheckpoint event, which may be later used as a point of reference forcomparisons (such as when identifying whether a shift event hasoccurred). And as time proceeds and further successive advertisingsignals from the ID node are detected, the master node may periodicallyupdate the benchmark checkpoint event used for such comparisons.Further, the master node may also only periodically report new checkmarkevents to the server as new summary checkpoint events. In other words,the master node may rely on benchmark checkpoint events as a type ofbaseline, identify new checkpoint events used to compare to the currentbaseline benchmark checkpoint event, update the benchmark checkpointevent with the new checkpoint event, and then only periodically reportnew checkpoint events to the server as a new summary checkpoint event.In summary, further embodiments may use benchmark checkpoint events aspart of enhanced processing and monitoring for event candidates thatfurther improves and simplifies management of the wireless node network.

FIGS. 42A-42D are detailed flow diagrams illustrating parts of anexemplary method for enhanced monitoring for an event candidate within awireless node network having a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node in accordance with an embodiment of the invention. Ingeneral, FIGS. 42A-42D describe exemplary steps performed by anexemplary master node when monitoring for an event candidate. As will beseen, such steps have the master node essentially scanning foradvertising signals and, once detecting a first signal from one of theID nodes, the master begins monitoring an event horizon related to thatparticular ID node in order to identify relevant node events and reportthe identified node events back to the server as event candidates havingparticular types of relevant event data. In general, such relevant eventdata for an event associated with an ID node may include timinginformation and observed signal strength information related to detectedadvertising signals, as well as information originally provided by theID node to the master node (e.g., sensor data such as a current batteryvoltage and/or a temperature value associated with the first ID node,and payload data provided by the first ID node). Those skilled in theart will appreciate that while the exemplary embodiment explained inFIGS. 42A-42D may involve determining a moving average as a way to helpavoid noise issues with advertising signal detections over time, otherembodiments with similar steps may deploy other types of statisticalrepresentations of the detected advertising signals when monitoring foran event candidate.

In more detail and referring now to FIG. 42A, method 4200 begins at step4202 with the master node scanning for advertising signals broadcastfrom one or more of the ID nodes. If the master node detects a firstsignal broadcast by a first of the ID nodes at step 4204, method 4200proceeds to step 4206. However, if the master node has not yet detecteda signal, method 4200 proceeds back to step 4202 to remain scanning foradvertising signals. At step 4206, the master node identifies the eventcandidate as a first sighting event related to the first ID node. Inresponse at step 4208, the master node generates event data representingthe first sighting event once the master node identifies the firstsighting event. Basically, the event data generated in step 4208represents the first sighting event and includes at least an identifierof the first ID node (e.g., a unique identifier related to the ID node,such as a media access control (MAC) address), and at least timinginformation and observed signal strength information characterizing thefirst sighting event. In more detail, such timing information andobserved signal strength information characterizing the first sightingevent may include a timestamp identifying when the master node detectedthe first signal and the observed signal strength value for the firstsignal (such as an observed or received RSSI value). At step 4210, themaster node reports the event data representing the first sighting eventto the server upon generating the event data representing the firstsighting event.

At step 4212, the master node may detect an alert flag reflecting astatus of the first ID node. For example, the alert flag may be part ofthe detected first advertising signal (e.g., a status in a portion ofthe signal's header) that indicates an alert stage for the ID node. Insome embodiments, the alert flag in the advertising signal header may beimplemented as a profile identifier that corresponds to one of severaldifferent operational profiles that may be used by the ID node.

If the alert flag is detected in step 4212, method 4200 may then proceedto step 4214. Otherwise, step 4212 proceeds directly to step 4216. Atstep 4214, the master node may change a sampling/reporting intervalrelative to this first ID node as a way to more frequently monitor andpossibly update the server about this first ID node. For example, themaster node may increase how frequently the master node updates theserver with reported event candidates and the related event data on thefirst ID node if the master node detects the alert flag is set. Inanother example, the master node may decrease how many detected signalsfrom the first ID node may be needed to qualify as a checkpoint event ifthe master node detects the alert flag is set. Thereafter, step 4214proceeds to step 4216 where the method 4200 has the master nodecontinuing to scan for additional advertising signals.

After step 4216 shown in FIG. 42A, method 4200 proceeds throughtransition (A) to FIG. 42B, where method 4200 continues at step 4218where the master node determines if a gap time has elapsed beforereceiving the next successive advertising signal from the first ID node.If so, then step 4218 proceeds to step 4220 as the master node will haveidentified the event candidate as a sporadic event. In other words, themaster node identifies the event candidate as a sporadic event when (1)the master node has not identified a first benchmark checkpoint eventrelated to the first ID node and (2) the master node has not detected asubsequent signal broadcast by the first ID node within a gap timeperiod from when the master node detected a most recent signal from thefirst ID node (e.g., the gap time has elapsed before a subsequent signalwas detected if any subsequent signal is detected at all).

At step 4222, the master node generates the event data representing thesporadic event, such as at least timing information and observed signalstrength information characterizing the sporadic event. In more detail,a further embodiment of method 4200 may have the timing information andobserved signal strength information characterizing the sporadic eventcomprising one or more of a timestamp on when the master node identifiedthe sporadic event, an average of observed signal strength value for anysignals broadcast by the first ID node and detected by the master nodefrom the first signal and before the gap time period elapsed, and acount of the signals broadcast by the first ID node and detected by themaster node from the first signal and before the gap time periodelapsed. Thereafter, at step 4224, the master node reports the eventdata representing the sporadic event to the server and then method 4200proceeds back to the beginning of method 4200 where the master nodebegins to scan for advertising signals again.

However, if the master node at step 4218 determines that the gap timehas not elapsed before receiving the next successive advertising signalfrom the first ID node, then step 4218 of method 4200 proceeds to step4226 where the master node continues to scan for additional successiveadvertising signals from the first ID node. At step 4228, if the masternode detects the next signal, method 4200 proceeds to step 4230 butotherwise goes back to step 4226 to continue scanning. At step 4230, themaster node determines if the gap time has elapsed before receivinganother successive advertising signal from the first ID node. If the gaptime has elapsed, the master node proceeds to step 4220 related toidentifying the event candidate as a sporadic event. However, if themaster node determines the gap time has not elapsed at step 4230 due toreceipt of another successive advertising signal from the first ID node,method 4200 proceeds to step 4232 where the master node furtherdetermines if it has detected/received an initial number of subsequentsuccessive signals broadcast from the first ID node. If not, the masternode is essentially still building up enough advertising signaldetections for a moving average window, and step 4232 proceeds back to4226 to continue scanning for more advertising signals from the first IDnode. However, if the master node has detected the initial number ofsubsequent successive signals broadcast from the first ID node in step4232, method 4200 proceeds to step 4234.

At step 4234, the master node determines a statistical representation ofthe initial number of subsequent successive signals (such as a firstmoving average of an observed signal strength value for the initialnumber of subsequent successive signals broadcast from the first ID node(including the first signal)) given that the elapsed time between eachof the initial number of subsequent successive signals is less than thegap time (which would have otherwise identified a sporadic type ofevent). Instead being considered a sporadic type of event under thistype of event criteria, method 4200 proceeds to step 4236 where themaster node identifies the event candidate as a first benchmarkcheckpoint event based upon the first moving average of observed signalstrength value determined in step 4234. The first benchmark checkpointevent represents a detected online state of the first ID node by themaster node, also referred to as an “online event” type of eventcandidate indicating the first ID node is essentially “online” with themaster node such that the master node is consistently receivingadvertising signals from the first ID node and observing parametersrelated to those signals as part of monitoring for other eventcandidates during the event horizon related to the first ID node. Atstep 4238, method 4200 has the master node generating the event datarepresenting the first benchmark checkpoint event once the master nodeidentifies the first benchmark checkpoint event in step 4236. Such eventdata representing the first benchmark checkpoint event comprises atleast timing information and observed signal strength informationcharacterizing the first benchmark checkpoint event. In more detail, afurther embodiment of method 4200 may have the timing information andobserved signal strength information characterizing the first benchmarkcheckpoint event as an online event comprising one or more of atimestamp on when the master node identified the first benchmarkcheckpoint event, the moving average of observed signal strength valueat the first benchmark checkpoint event, and a count of the signalsbroadcast by the first ID node and detected by the master node betweenthe identified first sighting event and the identified first benchmarkcheckpoint event. Thereafter, method 4200 proceeds to step 4240 wherethe master node reports the event data representing the first benchmarkcheckpoint event to the server before proceeding through transition (B)to step 4242 shown in FIG. 42C.

Referring now to FIG. 42C, the master node is again scanning forsuccessive advertising signals after identifying the first benchmarkcheckpoint event and reporting it to the server and determines if thegap time between the reception of the next successive advertisingsignals and the prior detected signal has elapsed at step 4242. If so,method 4200 may proceed to step 4244 where the master node identifiesthe event candidate as an offline event related to the first ID nodebecause (1) the master node previously identified the first benchmarkcheckpoint event related to the first ID node at step 4236 and (2) themaster node fails to detect a subsequent signal broadcast by the firstID node within the gap time period from when the master node detected amost recent of the subsequent successive signals from the first ID nodeas determined in step 4242. As such, method 4200 proceeds to step 4246where the master node generates event data representing the offlineevent comprising at least timing information and observed signalstrength information characterizing the offline event. In more detail, afurther embodiment of method 4200 may have the timing information andobserved signal strength information characterizing the offline eventcomprising one or more of a timestamp on when the master node identifiedthe offline event, the moving average of observed signal strength valuebetween a most recent benchmark checkpoint event and when the masternode identified the offline event, and a count of the signals broadcastby the first ID node and detected by the master node between the mostrecent benchmark checkpoint event and when the master node identifiedthe offline event. Thereafter, at step 4248, the master node reports theevent data representing the offline event to the server and then method4200 proceeds back to the beginning of method 4200 where the master nodebegins to scan for advertising signals again.

However, if method 4200 determines the gap time elapsed before receiptof another successive advertising signal at step 4242, method 4200proceeds to step 4250 where the master node continues to scan foradditional successive advertising signals from the first ID node. If themaster node detects another advertising signal in step 4252 and the gaptime has not elapsed, the method 4200 then moves to step 4256 where themaster node determines a next moving average of observed parameters(such as observed RSSI values) that includes this newly detected signal.Those skilled in the art will appreciate for embodiments that maysummarize the detected advertising signals using a statisticalrepresentation other than a moving average (such as a median or simplyan average over a set number of detected signals), step 4256 may beoptional given determining or generating such an alternative statisticalrepresentation may take place after receiving or detecting the next setof successive advertising signals (such as in step 4260).

However, if no new signal is detected in step 4252, method 4200 returnsto scanning in step 4250. And if the gap time has elapsed, then step4254 proceed to step 4244 so the master node can identify the eventcandidate as an offline event as described above.

Once the master node has determined the next moving average in step4256, the master node determines whether it has detected a subsequentthreshold number of advertising signals (and determined their respectivemoving averages) after most recent benchmark checkpoint event (e.g., thefirst benchmark checkpoint event from step 4236). If not, the masternode in method 4200 needs to continue scanning for additional successiveadvertising signals back in step 4250. But if so, method 4200 proceedsto step 4260 where the master node identifies a new checkpoint event andthen proceeds through transition (C) to step 4262 on FIG. 42D.

Referring now to FIG. 42D, the master node has now identified a newcheckpoint event (and determined a new moving average of observed signalstrength value for that point) and can perform additional analysis tosee if it can identify a shift event. In more detail, method 4200continues at step 4262 by comparing the moving average of the observedsignal strength value associated with the new checkpoint event and themoving average of the observed signal strength value associated with aprevious benchmark checkpoint event in order to determine a differencebetween these moving averages (i.e., ΔRSSI). Again, those skilled in theart will appreciate that other embodiments of method 4200 may use adifferent type of statistical representation associated with thebenchmark checkpoint comparison in step 4262 (such as comparingrespective averages of the observed signal strength values of thedetected advertising signals represented by the previous checkpointevent and the new checkpoint event).

From step 4262, method 4200 proceeds to step 4264 where the master nodedetects if a difference between the moving average of the observedsignal strength value associated with the new checkpoint event and themoving average of the observed signal strength value associated with aprevious benchmark checkpoint event at or above a threshold observedsignal strength difference value (i.e., whether ΔRSSI≥RSSI_(th)). If so,step 4264 proceeds to step 4266. If not, step 4264 proceeds to step4274.

At step 4266, the master node identifies the event candidate as a shiftevent related to the first ID node given the detected difference in step4264 is at or above the threshold observed signal strength differencevalue (i.e., RSSI_(th)). Method 4200 then proceeds to step 4268 wherethe master node generates event data representing the shift event thatcomprises at least timing information and observed signal strengthinformation characterizing the shift event. In more detail, a furtherembodiment of method 4200 may have the timing information and observedsignal strength information characterizing the shift event comprisingone or more of a timestamp on when the master node identified the shiftevent, the moving average of observed signal strength value between amost recent benchmark checkpoint event and when the master nodeidentified the shift event, and a count of the signals broadcast by thefirst ID node and detected by the master node between the most recentbenchmark checkpoint event and when the master node identified the shiftevent. Still further embodiments may have exemplary event data relatedto a shift event including slope information on whether the observedsignal strength is increasing or decreasing, and in some examples arelative value of such a slope. Thereafter, the master node reports theevent data representing the shift event to the server at step 4270.After step 4270, method proceeds to step 4272.

When step 4264 proceeds directly to step 4274 because the difference inthe moving averages is not yet at or above the threshold observed signalstrength difference value, step 4274 then has the master nodedetermining whether, upon identifying the new checkpoint event, themaster node as successfully identified a threshold number, z, ofsuccessive new checkpoint events since the last benchmark checkpointevent. If not, step 4274 proceeds directly to step 4272. However, if themaster node has successfully identified a threshold number, z, ofsuccessive new checkpoint events since the last benchmark checkpointevent (including the most recent new checkpoint event identified in step4260), the master node identifies the event candidate as a new summarycheckpoint event in step 4276, generates event data representing the newsummary checkpoint event (including at least timing information andobserved signal strength information characterizing the new summarycheckpoint event) in step 4278. In more detail, a further embodiment ofmethod 4200 may have the timing information and observed signal strengthinformation characterizing the new summary checkpoint event comprisingone or more of a timestamp on when the master node identified the newsummary checkpoint event, the moving average of observed signal strengthvalue between a most recent benchmark checkpoint event and when themaster node identified the new summary checkpoint event, and a count ofthe signals broadcast by the first ID node and detected by the masternode between the most recent benchmark checkpoint event and when themaster node identified the new summary checkpoint event. Thereafter, themaster node reports the event data representing the new summarycheckpoint event to the server in step 4280. After step 4280, method4200 proceeds to step 4272.

At step 4272, method 4200 has the master node replace event datarepresenting the previous benchmark checkpoint event with event datarepresenting the new checkpoint event as identified in step 4260 or newsummary checkpoint event as identified in step 4276. Thereafter, method4200 proceeds back through transition (B) to step 4242 to continuescanning for further successive advertising signals.

In still another embodiment, method 4200 may proceed further and havethe master node identifying the event candidate as a profile changeevent under particular conditions. In one example, the master node mayidentify the event candidate as a profile change event related to thefirst ID node when the master node observes an altered profile settingof the first ID node as reflected in the subsequent successive signalsbroadcast from the first ID node. Thereafter, the master node maygenerate event data representing the profile change event (comprising atleast timing information and observed profile setting informationcharacterizing the profile change event) and report the event datarepresenting the profile change event to the server upon generating theevent data representing the profile change event.

In another example, the master node may identify the event candidate asa profile change event related to the master node when the master nodealters a profile setting of master node. Thereafter, the master node maygenerate event data representing the profile change event (comprising atleast timing information and observed profile setting informationcharacterizing the profile change event) and report the event datarepresenting the profile change event to the server upon generating theevent data representing the profile change event.

Those skilled in the art will appreciate that method 4200 as disclosedand explained above in various embodiments may be implemented on anexemplary master node (e.g., exemplary master node 3410 in FIG. 35)running one or more parts of the master control and management code 425in conjunction with event detection engine code 3415 to perform steps ofmethod 4200 as described above. Such code may be stored on anon-transitory computer-readable medium, such as memory storage 415 onmaster node 3410. Thus, when executing such code, the master node may bespecially adapted to interact with other network devices (such as one ormore ID nodes as shown in FIG. 34 and server 3400 as shown in FIG. 34)as the master node's processing unit 400 is specially adapted to beoperative to perform algorithmic operations or steps from the exemplarymethods disclosed above, including method 4200 and variations of thatmethod.

In still another embodiment, a further exemplary master node apparatusfor enhanced monitoring for an event candidate within a wireless nodenetwork may be described as follows. The network may include a pluralityof ID nodes at the low level of the network and a server at the toplevel of the network. The master node apparatus in this embodiment,which fits in as a middle level element of the network, comprises a nodeprocessing unit, a memory storage, a timer, a first communicationinterface, and a second communication interface (e.g., such as exemplarymaster node 3410 and the internal exemplary circuit components as shownand described with respect to FIGS. 4 and 35). Each of the memorystorage, timer, and communication interfaces are respectively coupled tothe node processing unit of the master node apparatus. The memorystorage maintains at least an event detection engine code program moduleor application for execution by the node processing unit. The timercoupled to the node processing unit is operative to track an elapsedtime after an initiating event (such as after detecting an advertisingsignal that is broadcast from one of the ID nodes). The firstcommunication interface coupled to the node processing unit is operativeto communicate with at least a first of the ID nodes over a firstcommunication path (such as a signal path that supports low energyBluetooth® signals). The second communication interface coupled to thenode processing unit is operative to communicate with the server over asecond communication path (such as a cellular, LAN, or Wi-Fi signalpath). When executing the event detection engine code maintained on thememory storage, the node processing unit in the master node apparatusbecomes specially adapted and, thus, operative to interact with otherelements of the wireless node network while monitoring for an eventcandidate.

In particular, the node processing unit, as adapted under the executingcode stored in the memory storage, is operative to detect, via the firstcommunication interface, a first signal broadcast by a first of the IDnodes over the first communication path; identify the event candidate asa first sighting event related to the first ID node when the master nodedetects the first signal; generate event data representing the firstsighting event after identifying the first sighting event, where theevent data representing the first sighting event comprises an identifierof the first ID node and further comprises at least timing informationand observed signal strength information characterizing the firstsighting event; and cause the second communication interface to providethe event data representing the first sighting event to the server.

The node processing unit is further operative to monitor, via the firstcommunication interface, for any in a series of successive signalsbroadcast by the first ID node within an event horizon for the first IDnode after detecting the first signal; track, via coordination with thetimer, the elapsed time between successive ones of the first signal andany in the series of successive signals broadcast by the first ID node;and track a received signal strength indicator value for the firstsignal and any in the series of successive signals broadcast by thefirst ID node. As such, the node processing unit is also operative toidentify the event candidate as a subsequent event related to the firstnode and within the event horizon beginning with the first sightingevent, where the subsequent event is identified based upon timinginformation related to the elapsed time tracked by the timer and basedupon observed signal strength information as indicated by the receivedsignal strength indicator value; generate event data representing thesubsequent event as including at least the timing information related tothe elapsed time tracked by the timer and based upon observed signalstrength information as indicated by the received signal strengthindicator value; and cause the second communication interface to providethe event data representing the subsequent event to the server.

In a further embodiment of this master node apparatus, the subsequentevent may comprise a sporadic event, a first benchmark checkpoint event(also considered as an online event), an offline event, a shift event,and a new checkpoint event. In more detail, an embodiment may have thesubsequent event being a sporadic event when (1) the node processingunit has not identified a previous event within the event horizon to bea first benchmark checkpoint event representing detection of a thresholdnumber of the signals within the series of successive signals broadcastby the first ID node; and (2) the node processing unit has not detected,via the first communication interface, a subsequent signal broadcast bythe first ID node before the elapsed time exceeds a gap time period whentracked by the time from when the master node detected a most recent inthe series of successive signals from the first ID node.

In another embodiment of this master node apparatus, the subsequentevent may comprise a first benchmark checkpoint event representing adetected online state of the first ID node when the node processing unitdetects, via the first communication interface, a threshold number ofthe signals within the series of successive signals broadcast by thefirst ID node and without the elapsed time between each of the thresholdnumber of detected signals does not exceed a gap time period.

In still another embodiment of this master node apparatus, thesubsequent event may comprise an offline event when (1) the nodeprocessing unit identified a previous event within the event horizon tobe a first benchmark checkpoint event representing detection of athreshold number of the signals within the series of successive signalsbroadcast by the first ID node; and (2) the node processing unit has notdetected a subsequent signal broadcast by the first ID node when theelapsed time from when a most recent of the signals in the series ofsuccessive signals from the first ID node exceeds a gap time period.

In yet another embodiment of this master node apparatus, the subsequentevent may comprise a new checkpoint event when (1) the node processingunit has identified a previous event within the event horizon to be afirst benchmark checkpoint event, wherein the first benchmark checkpointevent representing detection of an earlier threshold number of thesignals within the series of successive signals broadcast by the firstID node; and (2) the node processing unit detects a subsequent thresholdnumber of the signals in the series of successive signals from the firstID node after identifying the first benchmark checkpoint event. In evenmore detail, an embodiment may have the node processing unit beingfurther operative to generate the event data representing the subsequentevent and cause the second communication interface to provide the eventdata representing the subsequent event to the server by being furtheroperative to (1) generate the event data representing the new checkpointevent upon identifying a threshold number of previous checkpoint events;and (2) cause the second communication interface to provide the eventdata representing the new checkpoint event to the server afteridentifying the threshold number of previous checkpoint events.

In a further embodiment of this master node apparatus, the subsequentevent may comprise a shift event when the node processing unit isfurther operative to detect at least a threshold difference between thereceived signal strength indicator value for the new checkpoint eventand the received signal strength indicator value for a previousbenchmark checkpoint event.

As noted in the above-described embodiments, enhanced monitoring fornode events to report as event candidates may involve comparing anobserved parameter of different detected advertising signals, which insome instances may also involve checkpoints that rely on the differentdetected advertising signals. A further embodiment makes such acomparison specifically based upon checkpoint summaries of the detectedadvertising signals. As such, the monitoring node (such as master node3410) may detect the different advertising signals but analyze andidentify potential event candidates based upon summarized groups or setsof such detected signals as checkpoints (also referred to as acheckpoint summary) successively generated internal to the monitoringnode.

In a general example, each group of 30 successively detected advertisingsignals from a broadcasting low level ID node maybe recorded and trackedby a monitoring master node as a checkpoint—a summarized representationof that group of signals. Each checkpoint summary has an observableparameter (such as an average RSSI value for the summarized group ofsignals) that can be compared against a similar observable parameter ofa previous checkpoint. If such a comparison reveals less than athreshold or relevant change compared to various event criteria, thecheckpoint summary may not be reported as representing a relevant eventcandidate. However, if the comparison lines up with event criteria toidentify a relevant node event for the ID node from the monitored changebased on the checkpoints, the monitoring master node may report the nodeevent as an event candidate to the server. Thus, an embodiment of themonitoring master node (or a system that uses such a monitoring masternode) may operate more efficiently in some deployments by identifyingthe event candidate based on successive checkpoints that providestatistically relevant observations of a lower level ID node.

FIG. 45 is a flow diagram illustrating an exemplary method for enhancedmonitoring for an event candidate within a wireless node network basedupon checkpoint summary points representing groups or sets of detectedadvertising signals in accordance with an embodiment of the invention.Referring now to FIG. 45, method 4500 is described where the wirelessnode network includes a plurality of ID nodes at a low level of thenetwork, a master node at a middle level in communication with the IDnodes, and a server at a top level in communication with the masternode—similar to that illustrated in FIG. 34. Method 4500 begins at step4505 where the master node receives a first set of advertising signalsbroadcast by a first of the ID nodes and then, at step 4510, generates afirst checkpoint summary representing the first set of advertisingsignals received by the master node. For example, if the first set ofadvertising signals detected included 10 signals, the first checkpointsummary may represent those 10 detected signals with a summarizedrepresentation (e.g., an average of the observed signal strength valuesfor each of the 10 detected signals).

At step 4515, method 4500 continues with the master node receiving asecond set of advertising signals broadcast by the first ID node afterthe first ID node broadcasts the first set of advertising signals, andthen at step 4520, generating a second checkpoint summary representingthe second set of advertising signals received by the master node. Thus,in the above example, the second set of advertising signals wouldinclude the next set of 10 successively detected advertising signalsfrom the ID node. As such, the second checkpoint summary may representthis next set of 10 detected signals and record an observed parameterrelative to this next set (such as an average of the observed signalstrength values for each of these next 10 detected signals).

At step 4525, method 4500 continues with the master node identifying theevent candidate based upon a comparison of an observed parameter foreach of the first checkpoint summary and the second checkpoint summary.In more detail, such an observed parameter for the checkpoint summariesmay be a statistical representation of the observed signal strengthvalues for the relevant set of advertising signals, such as a mean, amedian, an average, a moving average over a subset window of advertisingsignals, a moving average over a sliding time window, or a weightedaverage that represents the relevant set of advertising signals. Again,in the above described example, the master node (such as master node3410 as shown in FIGS. 34 and 35) may compare the average of theobserved signal strength values (such as a received signal strengthindicator (RSSI) value reflecting the observed signal strength) for thefirst 10 detected signals to the average of the observed signal strengthvalues for the next 10 detected signals as part of identifying the eventcandidate.

In more detail, further embodiments of method 4500 may identify theevent candidate in more detail relative to specific event criteria andthe results of the comparison. For example, the step of identifying theevent candidate in step 4525 may further comprise the master nodeidentifying the event candidate as an online event for the first ID nodewhen (a) a detected time gap between successive ones of the first set ofadvertising signals and the second set of advertising signals is lessthan the threshold time gap and (b) the master node has received atleast a threshold number of advertising signals from the first ID nodein the first set and the second set.

In another embodiment, the step of identifying the event candidate instep 4525 may further comprise the master node identifying the eventcandidate as a shift event for the first ID node when a differencebetween the observed parameter for the first checkpoint summary and theobserved parameter for the second checkpoint summary is at least athreshold value.

In still another embodiment, the step of identifying the event candidatein step 4525 may further comprise the master node identifying the eventcandidate as an offline event when a detected time gap between anysuccessive ones of the second set of advertising signals (afterdetecting the first set of advertising signals) is greater than thethreshold time gap during an event horizon for the first ID node asmonitored by the master node.

Further still, another embodiment may have step 4525 comprise the masternode identifying the event candidate as a sporadic event when the masternode receives at least one advertising signal from the first ID node butdoes not receive at least a threshold number of advertising signals fromthe first ID node within a defined period of time from when the masternode receives the at least one advertising signal. For example, themaster node may only detect 8 successively broadcast advertising signalsfrom the first ID node but then fail to detect the requisite 10 signalsthat would sufficiently make up the next set of signals for a checkpointsummary. Thus, in this example, the master node may identify what is tobe reported as an event candidate to be a sporadic event.

In yet another detailed embodiment, the step of identifying the eventcandidate in step 4525 may further comprise the master node identifyingthe event candidate as a checkpoint event when a periodic reportinginterval ends and based upon the comparison of the observed parameterfor the first checkpoint summary and the observed parameter for thesecond checkpoint summary. For example, the periodic reporting intervalused by the master node may comprise a threshold time period, which uponexpiration of this time period the master node then knows to report thesecond checkpoint summary as the checkpoint event (i.e., a type of eventcandidate reported to the server). In another example, the periodicreporting interval used by the master node may comprise a thresholdnumber of advertising signals received or detected or a threshold numberof checkpoint summaries generated since the last reported checkpointevent. Upon meeting that threshold number, the master node is thenpoised to subsequently report the second checkpoint summary as thecheckpoint event (i.e., a type of event candidate reported to theserver).

In still another embodiment of method 4500, step 4520 may have themaster node identifying the event candidate as a profile change eventwhen the comparison of the observed parameter for each of the firstcheckpoint summary and the second checkpoint summary indicates a firstobserved profile setting reflected in the first set of advertisingsignals is different than a second observed profile setting reflected inthe second set of advertising signals. The first observed profilesetting and the second observed profile setting may, in someimplementations of method 4500, relate to operation of the first IDnode, while they may relate to operation of the master node in otherimplementations of method 4500.

Further still, step 4520 may have the master node implementing the stepof identifying the event candidate by having the master node identifythe event candidate as a transmission power change event when thecomparison of the observed parameter for each of the first checkpointsummary and the second checkpoint summary indicates a first observedoutput power setting reflected in the first set of advertising signalsis different than a second observed output power setting reflected inthe second set of advertising signals.

In one alternative embodiment, the step of identifying the eventcandidate in step 4525 may further comprise the master node identifyingthe event candidate as an environmental change event when the comparisonof the observed parameter for each of the first checkpoint summary andthe second checkpoint summary indicates a second sensor data valueassociated with the second set of advertising signals is different thana first sensor data value associated with the first set of advertisingsignals. Sensor data values may be included in a header, for example, ofone or more of the advertising signals within a respective set. Thus,the master node may learn of environmental changes happening relative tothe first ID node through observed sensor data associated with each ofthe checkpoint summaries.

In another alternative embodiment, the step of identifying the eventcandidate in step 4525 may further comprise the master node identifyingthe event candidate as an environmental change event when the comparisonof the observed parameter for each of the first checkpoint summary andthe second checkpoint summary indicates a second sensor data valueassociated with the second set of advertising signals reflects adeparture from a first sensor data value associated with the first setof advertising signals, where the departure is more than a thresholddifference.

At step 4530, method 4500 continues with the master node havingidentified a relevant event candidate and then reporting the eventcandidate to the server. As this step is selectively performed only whenidentifying an event candidate, such a reporting step may have themaster node simplifying a data feed about the first ID node by sendingthe event candidate to the server as summary information reflecting anobserved change between the first set of advertising signals representedby the first checkpoint summary and the second set of advertisingsignals represented by the second checkpoint summary.

Additional embodiments of method 4500 may also include furtheralgorithmic steps. For example, another embodiment of method 4500 mayhave the master node also detecting a profile identifier from the firstID node. Such a profile identifier may be part of at least one of theadvertising signals in the first or second set of advertising signals.In response to detecting the profile identifier (e.g., a flag or otherdata included as part of an advertising signal's header), the masternode may then alter the periodic reporting interval based upon an alertprofile corresponding to the profile identifier. Such an alert profilemay include one or more different node management rules related tomonitoring the first ID node and reporting to the server.

Additionally, the periodic reporting interval may be based on a timefactor, such as a threshold time period adjustable by the master node.As such, the master node may adjust this reporting interval to morefrequently report checkpoint events as an identified event candidate,thereby updating the server more frequently. Alternatively, the periodicreporting interval may be based upon a threshold number of signalreceptions adjustable by the master node in similar fashion to increaseor decrease how frequently the monitoring master node provides updatesto the server in the form of an identified event candidate.

A further embodiment of method 4500 may also have the master noderesetting information collected based upon at least the first set ofadvertising signals and the second set of advertising signals afterreporting the checkpoint event to the server. This reset or clearing ofcollected information stored by the master node implements a type ofdata reduction that facilitates efficient use of the master node'sonboard resources.

Still another embodiment of method 4500 involves feedback from theserver after reporting the event candidate. In more detail, such afurther embodiment may have the master node receiving an adjustmentresponse from the server based upon the reported event candidate. Theadjustment response generated by the server based upon being notifiedabout the relevant event candidate may comprise an adjusted profile forat least one of the master node and the first ID node (e.g., changes toone or more node management rules maintained as part of an operationalprofile that governs how a particular wireless node in the network willfunction and communicate). Further still, the adjustment response maycomprise an adjusted profile for at least one of the other ID nodes,such as when a reported event candidate relative to the first ID nodehas the server changing how other ID nodes managed and monitored by themaster node will operate given the reported event candidate.Alternatively, the adjustment response may comprise updated context datareflecting the reported event candidate, such as updated context datareflecting a newly discovered source of RF interference in ananticipated proximate environment of the master node or the ID nodes inthe wireless node network.

Those skilled in the art will appreciate that method 4500 as disclosedand explained above in various embodiments may be implemented on anexemplary master node (e.g., exemplary master node 3410 in FIG. 35)running one or more parts of the master control and management code 425in conjunction with event detection engine code 3415 to perform steps ofmethod 4500 as described above. Such code may be stored on anon-transitory computer-readable medium, such as memory storage 415 onmaster node 3410. Thus, when executing such code, the master node may bespecially adapted beyond that of a generic computer to interact withother network devices (such as one or more ID nodes as shown in FIG. 34and server 3400 as shown in FIG. 34) as the master node's processingunit 400 is specially adapted to be operative to perform algorithmicoperations or steps from the exemplary methods disclosed above,including method 4500 and variations of that method.

In more detail, an embodiment of a master node apparatus for enhancedmonitoring for an event candidate based upon checkpoint summaries isdescribed as follows. The exemplary master node apparatus is deployed asa middle level wireless node element within a wireless node networkhaving a plurality of ID nodes at a low level and a server at a higherlevel within the network. In more detail, the exemplary master nodeapparatus in this embodiment generally comprises a node processing unit,a memory storage, a first communication interface, and a secondcommunication interface. The first communication interface is coupled tothe node processing unit and operative to communicate with at least afirst of the ID nodes over a first communication path (e.g., a shortrange wireless communication path, such as a Bluetooth® or NFC formattedshort range wireless data communications path). The second communicationinterface is coupled to the node processing unit and operative tocommunicate with the server over a second communication path (e.g., alonger range wireless communication path, such as a Wi-Fi or cellularlonger range wireless data communications path). The memory storage(e.g., memory storage 415 of master node 3410 shown in FIG. 35) is alsocoupled to the node processing unit (e.g., processing unit 400) andmaintains event detection engine code (e.g., code 3415) for execution bythe node processing unit.

In operation when executing the event detection engine code maintainedon the memory storage, the node processing unit executes the algorithmicinstructions of the code to perform particular and specially programmedfunctional steps as part of enhancing and improving how the master nodeapparatus interactively operates to monitor for an event candidate basedupon checkpoint summaries. In particular, the node processing unitbecomes operative, when executing the event detection engine code, todetect, via the first communication interface, a first set ofadvertising signals broadcast by a first of the ID nodes. Once the firstset of advertising signals has been detected, the node processing unitis then operative to generate a first checkpoint summary representingthe first set of advertising signals detected by the first communicationinterface. Similarly, the node processing unit is operative to detect,via the first communication interface, a second set of advertisingsignals broadcast by the first ID node after the first ID nodebroadcasts the first set of advertising signals and then generate asecond checkpoint summary representing the second set of advertisingsignals detected by the first communication interface. The nodeprocessing unit is then operative to compare an observed parameter (suchas observed signal strength value or RSSI as detected by the firstcommunication interface) for each of the first checkpoint summary andthe second checkpoint summary. This observed parameter, in more detail,may be a statistical representation of the respective advertisingsignals represented by the checkpoint summary, such as an averageobserved signal strength for each of the advertising signals associatedwith the particular checkpoint summary. Other examples of relevantstatistical representations of the observed signal strength value mayinclude a mean, a median, a moving average (relative to a time window ora window based on a number of detections), or a weighted average.

The node processing unit is then operative to identify the eventcandidate based upon the comparison of the observed parameter for eachof the first checkpoint summary and the second checkpoint summary, andcause the second communication interface to report the identified eventcandidate to the server over the second communication path. In moredetail, the second communication interface may transmit a message to theserver when reporting the identified event candidate, where the messagecomprises a reduced monitoring data feed about the first ID node that atleast includes summary information indicating an observed change betweenthe first set of advertising signals represented by the first checkpointsummary and the second set of advertising signals represented by thesecond checkpoint summary.

As part of identifying the event candidate, further embodiments of themaster node apparatus may have the node processing unit being operativeto identify the event candidate based on the comparison relative toparticular event criteria. For example, an embodiment of the master nodeapparatus may have the node processing unit being operative to identifythe event candidate as a sporadic event when the first communicationinterface detects at least one advertising signal from the first ID nodebut does not detect at least a threshold number of advertising signalsfrom the first ID node (a type of observed parameter) within a definedperiod of time from when the first communication interface detects theat least one advertising signal.

Another embodiment of the master node apparatus may have the nodeprocessing unit being operative to identify the event candidate as anonline event for the first ID node when (a) a detected time gap (a typeof observed parameter) between successive ones of the first set ofadvertising signals and the second set of advertising signals is lessthan the threshold time gap and (b) the first communication interfacehas received at least a threshold number of advertising signals from thefirst ID node (another type of observation relative to the advertisingsignals) in the first set and the second set.

A further embodiment of the master node apparatus may have the nodeprocessing unit being operative to identify the event candidate as ashift event for the first ID node when a difference between the observedparameter for the first checkpoint summary and the observed parameterfor the second checkpoint summary is at least a threshold value, such aswhen the average observed signal strength for the second checkpointsummary drops beyond a threshold level compared to the average observedsignal strength for the first checkpoint summary.

Still another embodiment of the master node apparatus may have the nodeprocessing unit being operative to identify the event candidate as anoffline event when a detected time gap (a type of observed parameter)between any successive ones of the second set of advertising signalsafter detecting the first set of advertising signals is greater than athreshold time gap during an event horizon for the first ID node.

Another embodiment of the master node apparatus may have the nodeprocessing unit being operative to identify the event candidate as acheckpoint event when a periodic reporting interval ends (whether theinterval is based on a time criteria or a number of detected signalscriteria) and based upon the comparison of the observed parameter forthe first checkpoint summary and the observed parameter for the secondcheckpoint summary.

An additional embodiment may have the node processing unit being furtheroperative to identify a profile identifier from the first ID node, suchas from a header part of at least one of the advertising signals ineither of the first set of advertising signals and the second set ofadvertising signals. Based upon the identified profile identifier, themaster node apparatus learns which alert profile is being used by thefirst ID node, and can then have the node processing unit alter theperiodic reporting interval based upon that alert profile correspondingto the profile identifier. As previously explained, the alert profilemay be one of a group of node management rules related to monitoring thefirst ID node and reporting to the server. In more detail, the periodicreporting interval may comprise a threshold time period adjustable bythe node processing unit in response to identifying the profileidentifier or, alternatively, may comprise a threshold number of signalreceptions adjustable by the node processing unit in response toidentifying the profile identifier.

Embodiments of the master node apparatus that monitors for an eventcandidate based on checkpoint summaries may also identify the eventcandidate as a type of change event. For example, the node processingunit may be operative to identify the event candidate as a profilechange event when the comparison of the observed parameter for each ofthe first checkpoint summary and the second checkpoint summary indicatesa first observed profile setting reflected in the first set ofadvertising signals is different than a second observed profile settingreflected in the second set of advertising signals. Such observedprofile settings may relate to operation of the first ID node, themaster node, or both.

In another example, the node processing unit may be operative toidentify the event candidate as a transmission power change event whenthe comparison of the observed parameter for each of the firstcheckpoint summary and the second checkpoint summary indicates a firstobserved output power setting reflected in the first set of advertisingsignals is different than a second observed output power settingreflected in the second set of advertising signals. The output powersetting for the ID node generating the advertising signal may appear aspart of the advertising signal itself (e.g., as part of the headerinformation, such as the “TX Power Level” information included inexample advertising packet 700 shown in FIG. 7).

In still another example, the node processing unit may be operative toidentify the event candidate as an environmental change event when thecomparison of the observed parameter for each of the first checkpointsummary and the second checkpoint summary indicates a second sensor datavalue associated with the second set of advertising signals is differentthan a first sensor data value associated with the first set ofadvertising signals or the comparison reflects a departure betweensensor data values that is more than a threshold difference. In moredetail, an exemplary sensor on the ID node may provide changing sensordata over time and, as successive advertising signals are broadcast fromthe ID node, sensor data values are provided as part of the successivelybroadcasted advertising signals. Thus, the node processing unit of themaster node apparatus may compare such observed sensor data over time toidentify an environmental change event (e.g., a package associated withthe ID node is experiencing a rapid increase in temperature, which maybe due to where it has been placed (next to a heat source or in the sun)or due to the contents of the package creating heat (such as from anundesired chemical reaction or from internal burning of the contents).

Further embodiments of the master node apparatus that monitors for anevent candidate based on checkpoint summaries may also involve receivingand responding to server feedback based on the reported event candidate.For example, the node processing unit may be further operative toreceive, via the second communication interface, an adjustment responsefrom the server based upon the event candidate. Such an adjustmentresponse received over the second communication interface may be amessage from the server that may include an adjusted profile for themaster node apparatus, the first ID node, or one of the other ID nodesbeing managed by the master node apparatus. Such an adjusted profile maybe one or more revised or new node management rules that govern anddefine how the particular wireless node element operates—such as a powerlevel to use, a frequency of broadcasting advertising signals, etc.Likewise, the adjustment response may be a message with updated contextdata reflecting the reported event candidate.

Those skilled in the art will understand that the above describeddifferent embodiments of the master node apparatus that monitors for anevent candidate based on checkpoint summaries as described above(consistent with the description above related to method 4500 and itsvariations), may also be deployed as part of a larger monitoring systemthat identifies an event candidate based on checkpoint summaries withina wireless node network. Such a monitoring system may include a serverdisposed at a top level of the network, an ID node disposed at a lowerlevel of the network that is broadcasting advertising signals, and amaster node disposed at a middle level of the network. The ID node maybe associated with a package being shipped and tracked, while the masternode takes the role of monitoring signals from the ID node as the IDnode comes within a communication range of the master node. The masternode, as particularly described in the embodiments above, operates todetect advertising signals, generate successive checkpoint summaries,compare an observed parameter for each of the successive checkpointsummaries to identify the event candidate, and cause the secondcommunication interface on the master node to report the identifiedevent candidate to the server. The server, as part of the monitoringsystem, is operative to receive the identified event candidate from themaster node and transmit a responsive adjustment response to the masternode based upon the identified event candidate. Such a responsiveadjustment response provided as feedback to the master node comprises atleast one of an adjusted profile for the master node, an adjustedprofile for the ID node, and updated context data reflecting theidentified event candidate.

As noted in some of the above-described embodiments, enhanced monitoringfor node events to report as event candidates may involve generating acheckpoint summary (also referred to generally as a checkpoint) thatessentially summarizes and represents a set or group of advertisingsignals broadcast by lower level ID nodes. In a further embodiment,reporting each generated checkpoint to the server as a type of eventcandidate to be processed by the server may still provide a degree ofsystem-level improvement that lessens the monitoring and reportingburden placed on the monitoring master node. In other words, deployinguse of checkpoints as a monitoring and tracking mechanism carried out bythe master node at an intermediate level of the wireless node network(as an apparatus itself or as an apparatus element of a system) mayeffectively reduce the master node monitoring data feed to the backendmanaging server of such a system when compared to simply sending the rawdata of each advertising signals detected by the master node to theserver.

In a general example, each group of 30 successively detected advertisingsignals from a broadcasting low level ID node may be recorded andtracked by a monitoring master node as a checkpoint—a summarizedrepresentation of that group of signals. Each checkpoint summary has anobservable parameter (such as an average RSSI value for the summarizedgroup of signals) that, in a basic exemplary embodiment, can be reportedto the server by the monitoring master node as a way of monitoring foran event candidate. In this basic example, the summarized representationof that group of signals (e.g., the average RSSI value for the group of30 detected advertising signals) may be reported as an event candidaterelative to the broadcasting and monitored ID node. Such a reportedevent candidate (via the reported checkpoint) has the monitoring masternode informing the server that the broadcasting ID node is “stillhere”—useful information in and of itself to the server when managingelements of the wireless node network.

Furthermore, embodiments of methods, apparatus, and systems that monitorfor node events to report as event candidates may extend how amonitoring master node uses a checkpoint so that not all checkpoints maybe reported, but only certain of the summarized checkpoints. Forexample, a further embodiment involving checkpoints may have themonitoring master node generating successive checkpoint summaries overtime (each being based on different groups or sets of detectedadvertising signals from an ID node) and then comparing an observedparameter of different checkpoint summaries. In more detail, theobservable parameter (such as average RSSI value) for a currentlygenerated checkpoint can be compared against a similar observableparameter of a previous checkpoint. If such a comparison reveals lessthan a threshold or relevant change compared to various event criteria,the checkpoint summary may not be reported as representing a relevantevent candidate. However, if the comparison lines up with event criteriato identify a relevant node event for the ID node from the monitoredchange based on the checkpoints, the monitoring master node may reportthe node event as an event candidate to the server.

As such, the monitoring node (such as master node 3410) may detect eachof the different advertising signals but analyze and identify potentialevent candidates based upon the checkpoints successively generatedinternal to the monitoring node. In some cases, the monitoring masternode analyzes and identifies potential event candidates based upon acomparison of different checkpoint summaries. In this way, what may bereported to the server may advantageously be refined or intelligentlydistilled node event information on what is happening with a particularID node. Thus, various embodiments of the monitoring master node (or asystem that uses such a monitoring master node) may operate moreefficiently in some deployments by identifying the event candidate basedon one or more successive checkpoints that provide statisticallyrelevant observations of a lower level ID node indicative of a status ofthe relevant ID node.

FIG. 46 is a flow diagram illustrating another exemplary method forenhanced monitoring for an event candidate within a wireless nodenetwork based upon a checkpoint summary in accordance with an embodimentof the invention. The exemplary wireless node network has a plurality oflower level ID nodes, a master node at a middle level in communicationwith the ID nodes, and a server at a top level in communication with themaster node. Referring now to FIG. 46, exemplary method 4600 begins atstep 4605 with the master node activating a monitoring mode of operationthat listens for one or more broadcast signals emitted from any of theID nodes without prompting the ID nodes for transmission of the one ormore broadcast signals from the ID nodes. For example, in contrast toconventional RFID tag responses, which must be prompted by an RFID tagreader, the master node may activate a monitoring mode that does notrequire prompting the ID nodes to broadcast but, instead, listens forwireless ID nodes that may be broadcasting short-range advertisingpacket signals.

At step 4610, if the master node receives a first advertising signalbroadcast by a first of the ID nodes in the wireless node network,method 4600 proceeds from step 4610 directly to step 4615. Otherwise,step 4610 remains in the activated monitoring mode awaiting receipt of asignal.

At step 4615, method 4600 proceeds with the master node recording anobserved parameter related to the received first advertising signalbroadcast by the first ID node. Such an observed parameter may, forexample, be an observed signal strength level for the signal or observedinformation within a part (e.g., a header) of the detected advertisingsignal. The observed parameter may be recorded into volatile and/ornon-volatile memory depending on the deployment, memory writing speedavailable with accessible memory on the master node, and a need ordesire to avoid loss of data due to unintentional power loss.

With the first advertising signal received by the master node at step4610 and the observed parameter for that signal recorded at step 4615,method 4600 proceeds to step 4620 to detect successive advertisingsignals broadcast by the first ID node. Thus, as a next advertisingsignal broadcast from the first ID node is received at step 4620, step4620 directly proceeds to step 4625. Otherwise, step 4620 remains in theactivated monitoring mode awaiting receipt of more advertising signalsfrom the first ID node.

At step 4625, method 4600 proceeds with the master node recording theobserved parameter related to the next successively received advertisingsignal broadcast by the first ID node. In more detail, such an observedparameter of the received advertising signals may, for example, be areceived signal strength indicator (RSSI) value reflecting a signalstrength as detected by the master node. In another example, theobserved parameter may be sensor data provided by the first ID node andcaptured by the master node related to the first ID node. For instance,the advertising signals broadcast by the first ID node may includesensor data within the advertising signals' header portion. Such sensordata may be observed by the master node through the detected advertisingsignals, and indicate low level ID node activity or status (e.g., atemperature condition sensed by the ID node or humidity condition sensedby the ID node).

At step 4630, the master node determines if the received signals (i.e.,those advertising signals received in step 4610 and in 4620) amount to asufficient number of received signals that corresponds to apredetermined group of advertising signals that include the firstadvertising signal and a subsequent group of successively receivedadvertising signals. If not, step 4630 returns to step 4620 and awaitsreceipt of further advertising signals. However, if so, step 4630proceeds to step 4635.

In some embodiments, the number of signals that make up thepredetermined group may be defined by the server. For example, theserver may provide the master node with node management information inthe form of a particular number of advertising signals deemed to make upthe predetermined group for purposes of monitoring and reporting asexplained with reference to embodiments of method 4600. In otherembodiments, this number may be dynamically altered by the master nodeand/or the server as monitoring continues. For example, the master nodemay detect the broadcasting ID node has raised an alert (e.g., anincreased alert status, a change in profile status, a change inenvironmental status based on sensor data, and the like) where themaster node then is able to self-adapt its monitoring by changing thenumber of signals in the predetermined group or, in other instances,report the alert to the server so the server may dictate a change in thenumber of signals in the predetermined group and refine the monitoringprocess from the server level of the network via a node managementmessage sent to the master node with the changed number of signals inthe group for monitoring purposes.

At step 4635, method 4600 proceeds to generate a checkpoint summarybased on the received advertising signals. More specifically, the masternode generates a first checkpoint summary representing a first set ofadvertising signals comprising the received first advertising signal(the signal received in step 4610) and the successively receivedsubsequent group of advertising signals (the signals that weresuccessively received at step 4630). The first checkpoint summary is atransformative data representation of the first set of advertisingsignals and includes a summary observed parameter generated based uponthe recorded observed parameter related to the received firstadvertising signal broadcast (as recorded in step 4615) and the recordedobserved parameter related to each of the successively receivedsubsequent group of advertising signals (as recorded in step 4625). Inmore detail, the summary observed parameter for the first checkpointsummary may be implemented as a statistical representation of theobserved signal strength values for the first set of advertisingsignals. Such a statistical representation of the observed signalstrength values may be implemented using a mean, a median, an average, amoving average over a subset window of advertising signals, a movingaverage over a sliding time window, or a weighted average related to theobserved signal strength values (or captured sensor data) from the firstset of advertising signals.

At step 4640, method 4600 proceeds with the master node transmitting thefirst checkpoint summary to the server as the event candidate relativeto the first ID node. More specifically, step 4640 may have the masternode simplifying a data feed for the server related to a status of thefirst ID node by sending the event candidate to the server indicating asummarized monitored status of the first node based upon the summaryobserved parameter of the first checkpoint summary. Thus, transmittingas performed in step 4640 enhances the monitoring master node to serverreporting overhead and improves the overall efficiency of informing thesystem's server about an event candidate via the reported firstcheckpoint summary.

While step 4640 explained above has the first checkpoint summaryreported as the event candidate, in further embodiments of method 4600,the transmitting in step 4640 may occur based upon a periodic reportinginterval criteria. In particular, a further embodiment may implementstep 4640 with the master node transmitting the first checkpoint summaryto the server as the event candidate relative to the first ID node whenthe first checkpoint summary meets a periodic reporting intervalcriteria relative to one or more prior checkpoint summaries generated bythe master node, such as transmitting only every 5^(th) checkpointsummary while the other prior checkpoint summaries remain internal tothe monitoring master node.

In a more detailed embodiment, transmitting in step 4640 may furthercomprise having the master node incrementing a checkpoint count inmemory of the master node upon generating the first checkpoint summary;having the master node compare the incremented checkpoint count to theperiodic reporting interval criteria relative to one or more priorcheckpoint summaries generated by the master node; and using the masternode to report the first checkpoint summary to the server as the eventcandidate when the incremented checkpoint count matches the periodicreporting interval criteria (e.g., when the first checkpoint summary isa 5^(th) checkpoint summary relative to the last reported checkpointsummary). The periodic reporting interval criteria may identify athreshold number of generated checkpoint summaries as a reportingcondition for reporting the first checkpoint summary to the server asthe event candidate. Such a threshold number may be predetermined insome embodiments (e.g., report only every 5^(th) checkpoint summary)while other embodiments may have the master node adjust such a thresholdnumber.

In more detail relative to adjusting the periodic reporting intervalcriteria, a further embodiment of method 4600 may further have themaster node detect a profile identifier from the first ID node. Theprofile identifier may, for example, be part of at least one of thereceived first advertising signal and the successively receivedsubsequent group of advertising signals (such as information in a headerof one of the broadcasted advertising signals). The master node may thenrespond to this detected profile identifier, and alter the periodicreporting interval criteria based upon an alert profile corresponding tothe profile identifier. The alert profile includes node management rulesrelated to monitoring the first ID node and reporting to the server.Thus, the alert profile for the first ID node (as indicated by theprofile identifier) may reflect that the ID node needs quick attention,warranting the monitoring master node to change how frequently it mayreport checkpoint summaries to the server. For example, the first IDnode may autonomously switch to using the alert profile as it may haveentered a particular Alert Stage (as previously described), and themonitoring master node may then advantageously adapt to how thatparticular ID node is monitored by adjusting the periodic reportinginterval criteria so that event candidate information on the ID node ismore frequently transmitted to the server within the system.

In another further embodiment, method 4600 may also have the master nodeadjusting the summary observed parameter to be reported. In particular,the master node may adjust the summary observed parameter so that itstatistically summarizes the first checkpoint summary with at least oneprevious checkpoint summary generated by the master node and notreported to the server. For example, the master node may adjust thesummary observed parameter to be reported to the server to be an averageof the current (first) checkpoint summary and four previously unreportedsummary observed parameters for previous checkpoint summaries notreported. In this manner, the adjusted summary observed parametersprovide a statistical representation of the ID node's status since thelast checkpoint summary was reported as an event candidate.

In a more detailed embodiment, method 4600 may have the master nodereporting the event candidate to the server based upon a comparison ofthe current (first) checkpoint summary to a prior checkpoint. Forexample, this embodiment of method 4600 may also include having themaster node comparing a previous summary observed parameter for aprevious checkpoint summary to the summary observed parameter for thefirst checkpoint summary to identify a change in a status of the firstID node. As such, the master node may then transmit the first checkpointsummary to the server as the event candidate when the comparisonidentifies the change in the status of the first ID node. Such a changein the first ID node's status may, for example, be when the previoussummary observed parameter for the previous checkpoint summary isdifferent than the summary observed parameter for the first checkpointsummary by more than a threshold level. More specifically, an exemplarychange in the first ID node's status identified from the comparison maybe a node event, such as a sporadic event indicating an abbreviatedevent horizon for the first ID node; an online event indicating abeginning of a monitored event horizon for the first ID node; a shiftevent indicating at least a threshold difference between the previoussummary observed parameter for the previous checkpoint summary and thesummary observed parameter for the first checkpoint summary; and anoffline event indicating an end of the monitored event horizon for thefirst ID node. Further still, an exemplary change in the first ID node'sstatus identified from the comparison may be a node event such as aprofile change event indicating the first ID node changed a profilesetting during a monitored event horizon for the first ID node; atransmission power change event indicating the first ID node changed anoutput power setting during the monitored event horizon; and anenvironmental change event indicating a change in sensor data capturedby the first ID node during the monitored event horizon.

Those skilled in the art will appreciate that method 4600 as disclosedand explained above in various embodiments may be implemented on anexemplary master node (e.g., exemplary master node 3410 in FIG. 35)running one or more parts of the master control and management code 425in conjunction with event detection engine code 3415 to perform steps ofmethod 4600 as described above. Such code may be stored on anon-transitory computer-readable medium, such as memory storage 415 onmaster node 3410. Thus, when executing such code, the master node may bespecially adapted beyond that of a generic computer to interact withother network devices (such as one or more ID nodes as shown in FIG. 34and server 3400 as shown in FIG. 34) as the master node's processingunit 400 is specially adapted to be operative to perform algorithmicoperations or steps from the exemplary methods disclosed above,including method 4600 and variations of that method.

Further still, those skilled in the art will appreciate that such anexemplary master node adapted to perform algorithmic operations or stepsfrom the exemplary methods disclosed above, including method 4600 andvariations of that method, may be deployed as part of a node monitoringsystem embodiment that identifies an event candidate within a wirelessnode network. Such an exemplary monitoring system comprises a serverdisposed at a top level of the network, an ID node disposed at a lowerlevel of the network that is broadcasting advertising signals, and amaster node disposed at a middle level of the network. The ID node maybe associated with a package being shipped and tracked, while the masternode takes the role of monitoring broadcasted advertising signals fromthe ID node as the ID node comes within a communication range of themaster node. The master node further comprises a master node processingunit, a memory storage, and first and second communication interfaces.The master node's memory storage is coupled to the master nodeprocessing unit maintains event detection engine code for execution bythe master node processing unit (e.g., memory storage 415 maintainingevent detection engine code 3415 for execution by processing unit 400 asshown and explained with reference to FIG. 35). The first communicationinterface is coupled to the master node processing unit and operative tocommunicate with the ID node over a first communication path, while thesecond communication interface is also coupled to the master nodeprocessing unit and operative to communicate with the server over asecond communication path. As such, the first communication path isdifferent from the second communication path similar to that shown inFIG. 34 where the first communication path from the master node 3410 tothe ID nodes 120 a-e is distinct and separate from the communicationpath from master node 3410 to server 3400 via network 105.

As a monitoring and reporting elements within the monitoring system, themaster node, when executing the event detection engine code on themaster node processing unit, is operative to cause the firstcommunication interface to listen for one or more broadcast signalsemitted from the ID node without prompting the ID node for transmissionof the one or more broadcast signals from the ID node. The master node(via its master node processing unit and other elements) is then furtheroperative to detect, via the first communication interface, a firstadvertising signal broadcast by the ID node and record a first observedparameter in the memory storage based upon the detected firstadvertising signal broadcast by the ID node. The master node is thenoperative to successively detect, via the first communication interface,a subsequent group of advertising signals broadcast by the ID node, andrecord a subsequent group of observed parameters where each are basedupon a respective one of the successively received subsequent group ofadvertising signals broadcast by the ID node.

In more detail, each of the first observed parameter and the subsequentgroup of observed parameters may be a received signal strength indicator(RSSI) value reflecting a signal strength as detected by the masternode. As such, the master node monitors for the ID node advertisingsignals and, in particular, observes the RSSI value for such signals.However, in another more detailed system embodiment, each of the firstobserved parameter and the subsequent group of observed parameters maybe one of a plurality of sensor data captured by the master node relatedto the ID node. As such, the master node monitors for the ID nodeadvertising signals and, in particular, observes sensor data within suchadvertising signals (such as environmental sensor data, packagemonitoring sensor data, or other sensor data generated by the ID nodeand included within advertising signals broadcast from that ID node) asthe observed parameters.

With the detected advertising signals and observed parameters for eachof such signals, the system's master node is then operative to generatea first checkpoint summary representing a first set of advertisingsignals comprising the detected first advertising signal and thesuccessively detected subsequent group of advertising signals. Morespecifically, the generated first checkpoint summary comprises a summaryobserved parameter generated based upon the recorded observed parameterbased upon the detected first advertising signal broadcast and each ofthe recorded observed parameters respectively based upon thesuccessively detected subsequent group of advertising signals. Thesystem's master node then is operative to cause the second communicationinterface to report the first checkpoint summary over the secondcommunication path to the server as the event candidate relative to theID node.

The system's server (such as server 3400 depicted in FIGS. 34 and 36) isoperative to receive the event candidate from the master node andtransmit a responsive adjustment response to the master node based uponthe event candidate. Such a responsive adjustment response generated andtransmitted by the system's server (e.g., server 3400) comprising atleast one of an adjusted profile for the master node, an adjustedprofile for the ID node, and updated context data reflecting theidentified event candidate.

In more detail, such a system embodiment may have the system's masternode processing unit being further operative to generate the summaryobserved parameter for the first checkpoint summary as a statisticalrepresentation of the observed signal strength values for the first setof advertising signals broadcast by the ID node. Such a statisticalrepresentation of the observed signal strength values may be implementedas a mean, a median, an average, a moving average over a subset windowof advertising signals, a moving average over a sliding time window, ora weighted average of the observed signal strength values.

In a further system embodiment, reporting of the checkpoint as the eventcandidate may be more periodic than done for each checkpoint. Forexample, the master node processing unit may be operative to cause thesecond communication interface to report the first checkpoint summary tothe server by being further operative to determine if the firstcheckpoint summary meets a periodic reporting interval criteria relativeto one or more prior checkpoint summaries generated by the master nodeand stored within the memory storage of the master node. The master nodemay then be operative to cause the second communication interface totransmit the first checkpoint summary to the server as the eventcandidate only when the first checkpoint summary meets the periodicreporting interval criteria (such as when such criteria is defined asreporting every over checkpoint or every 5^(th) checkpoint). The masternode's processing unit, under such a periodic reporting regimen, may befurther operative to adjust the summary observed parameter tostatistically summarize the first checkpoint summary with at least oneprevious checkpoint summary generated by the master node and notreported to the server.

Further still, the master node processing unit may be operative to causethe second communication interface to report the first checkpointsummary to the server by being further operative to increment acheckpoint count upon generating the first checkpoint summary. Thecheckpoint count may be a data structure (e.g., event data 3500)generated and maintained within memory of the master node. Theprocessing unit is then operative to compare the incremented checkpointcount to a periodic reporting interval criteria relative to one or moreprior checkpoint summaries generated by the master node, and cause thesecond communication interface to transmit the first checkpoint summaryto the server as the event candidate only when the incrementedcheckpoint count matches the periodic reporting interval criteria. Sucha periodic reporting interval criteria may, in some embodiments,identify a threshold number of generated checkpoint summaries as areporting condition for reporting the first checkpoint summary to theserver as the event candidate.

In still another system embodiment, the master node processing unit maybe operative to detect, via the first communication interface, a profileidentifier from the ID node. Such a profile identifier may be part of atleast one of the detected first advertising signal and the successivelydetected subsequent group of advertising signals (e.g., a portion of theadvertising signal's header that includes relevant profile identifierdata). Based upon an alert profile corresponding to the profileidentifier, the master node processing unit may then be operative toalter the periodic reporting interval criteria, where the alert profilemay include a plurality of node management rules related to monitoringthe ID node and reporting to the server.

Similar to the variations to exemplary method 4600 as described above,the above-described system embodiment may be extended to involvecomparing prior checkpoints. For example, in a further systemembodiment, the system's master node processing unit may be furtheroperative to access the memory storage for a previous summary observedparameter for a previous checkpoint summary and then compare theprevious summary observed parameter to the summary observed parameterfor the first checkpoint summary to identify a change in a status of theID node. Accordingly, the second communication interface of the system'smaster node may transmit the first checkpoint summary to the server asthe event candidate if the master node processing unit identifies thechange in the status of the ID node by comparing the previous summaryobserved parameter to the summary observed parameter for the firstcheckpoint summary. Such a change in the status of the system's ID nodemay comprise a monitored node condition when the previous summaryobserved parameter for the previous checkpoint summary is different thanthe summary observed parameter for the first checkpoint summary by morethan a threshold level. In a more detailed system embodiment, the changein the status of the ID node may identify the first checkpoint summaryas a particular node event, such as a sporadic event indicating anabbreviated event horizon for the ID node; an online event indicating abeginning of a monitored event horizon for the ID node; a shift eventindicating at least a threshold difference between the previous summaryobserved parameter for the previous checkpoint summary and the summaryobserved parameter for the first checkpoint summary; and an offlineevent indicating an end of the monitored event horizon for the ID node.Further still, another embodiment may have the change in the status ofthe ID node identifying the first checkpoint summary as a particularnode event, such as a profile change event indicating the ID nodechanged a profile setting during a monitored event horizon for the IDnode; a transmission power change event indicating the ID node changedan output power setting during the monitored event horizon; and anenvironmental change event indicating a change in sensor data capturedby the ID node during the monitored event horizon.

In summary, various embodiments of methods, apparatus, and systemsinvolve operation of an exemplary master node (as an interactivemonitoring device or as part of a system) that provides the enhancedability to monitor elements of a wireless node network for eventcandidates related to a variety of different type of node events andreport them in an intelligent and efficient manner to a higher levelserver in the network. Such enhanced monitoring for event candidatesprovides a foundation for improved operations of a wireless node network(such as a network of node elements used in logistics tracking andlogistics management of items being shipped as they are respectivelyassociated with different low level ID nodes).

Server Operations Related to Enhanced Management via Event CandidateProcessing

While the exemplary master node described above provides for enhancedmonitoring of an event candidate and reporting of the event candidate tothe server, further embodiments may focus on the server (such as theserver 3400 illustrated and described above with respect to FIGS. 34 and36) and how it may be specially adapted to apply an analytics type ofprocess to rank or score the received event candidate as part of“learning” from the reported information—e.g., determining how closelythe event correlates with other server-accessible data representingknown node relevant activity and adjusting management operationsaccordingly. Those skilled in the art will appreciate that suchembodiments may apply feature extraction functionality using astatistical measure, and the classification of features into correctcategories based on their characteristics (such as whether an eventcandidate is a type of node event that can be confidently attributed toknown node relevant activity). In doing so, embodiments operate on datathat is transformational in nature. For example and as concretelyapplied in embodiments described herein, the event data sent as part ofthe event candidate is representative of node events and may betransformed by the server into updated node management information.

The updated, adjusted, changed or refined node management information(such as relevant node management context data and/or relevant nodemanagement rules data) may be used by the server to help manage otherelements of the network (such as a master node or ID nodes in thenetwork). For example, based upon a reported event candidate, the servermay provide feedback to the master node to alter or otherwise update howthe master node operates itself and/or how the master node manages oneor more of the ID nodes under its control via updated context data orupdated node management rules (e.g., revised operational profiles thedefine how a master node or ID node functions, operates, reports toother nodes, etc.). In other words, embodiments may deploy a systemhaving the master node monitoring for one or more event candidatesintegrated with backend server analytics-type processing where eventcandidates may be ranked for confidence of being correlated to known ornew node relevant activity as a type of input for improved management ofnodes in the network and enhanced quality/efficiency of how node eventinformation may be captured and reported as a basis for wireless nodenetwork management.

As explained above, FIG. 36 is a more detailed diagram of exemplaryserver 3400 in the network illustrated in FIG. 34 that operates toreceive an event candidate and manage the network based upon the eventcandidate in accordance with an embodiment of the invention. Exemplaryserver 3400, as shown and described relative to FIG. 36, may be deployedas part of the methods described below with respect to FIGS. 43 and 44.In more detail, FIG. 43 is a flow diagram illustrating an exemplarymethod for enhanced management of a wireless node network based uponreceipt of and processing of an event candidate in accordance with anembodiment of the invention. Referring now to FIG. 43, method 4300begins at step 4305 with the server receiving an event candidateidentified by the master node.

In one embodiment of method 4300, the event candidate is related to afirst of the ID nodes and represents an updated status related to thefirst ID node. In another embodiment, the updated status related to thefirst ID node may comprise a shift in signal strength in what isbroadcast by the first ID node (such as when the master node observed asignificant decrease in RSSI values for advertising signals from thefirst ID node as identified when the event candidate is a shift event).In more detail, the updated status may comprise a changed status of thefirst ID node, an unchanged status of the first ID node, or a summarizedcheckpoint status of the first ID node (such as reflected by a firstbenchmark checkpoint event or a new summary checkpoint event.

Further still, another embodiment of method 4300 may have the eventcandidate be related to a subset of the ID nodes including the first IDnode. For example, the event candidate reported may reflect anidentified shift event for each of the subset of ID nodes.

At step 4310, method 4300 proceeds with the server generating apredictive score for the event candidate based upon context datamaintained by the server and related to the first ID node, where thepredictive score focuses on whether the event candidate corresponds to anode related activity. More particularly, the predictive score maycomprise a confidence factor related to whether the event candidatecorresponds to the node related activity. In one example, the noderelated activity may be a detectable physical activity (e.g., a vehicledriving in close proximity to the node or the node moving on aparticular conveyance device or system) and a detectable electromagneticactivity (e.g., RF noise generated by a motor or other engine nearby anode). In another example, the node related activity may comprise ananticipated activity characterized by at least a portion of the contextdata related to the first ID node (e.g., an anticipated movement througha tunnel that may shield the node from receiving communications fromother nodes). Further still, the node related activity may comprise anew physical or electromagnetic node related activity not alreadycharacterized by the context data related to the first ID node.Additional examples of the node related activity may include movement ofat least one of the first ID node, the master node, and an object nearthe master node; exposure to a source of RF interference; and placementof the first ID node within a container (such as a shipping container,ULD container, a vehicle that operates as a type of container (e.g.,delivery van, tractor trailer, and the like)).

In more detail, generating the predictive score for the event candidatein step 4310 may be based upon an evaluation of the event candidateagainst at least a portion of the context data related to the first IDnode (such as context data 560 and that maintained in context database565). In further embodiments, exemplary context data that may be part ofthis portion used when generating the predictive score may come in avariety of forms, such as one or more of scan data related to the firstID node, scan data related to the master node, scan data related to asecond master node in the wireless node network, scan data related to asecond of the ID nodes, historic data related to the first ID node,historic data related to the master node, historic data related to asecond master node in the wireless node network, historic data relatedto a second of the ID nodes, shipment data related to an item beingshipped with the first ID node, layout data related to an anticipatedenvironment for the first ID node, RF data related to an anticipatedsignal path environment for the first ID node, and third party dataoriginating from outside the wireless node network and relating to ananticipated physical condition to be faced by the first ID node.

In a further embodiment, method 4300 may have step 4310 generating thepredictive score for the event candidate by having the server identify apattern match between the event candidate and at least a portion of thecontext data related to the first ID node, and then assigning a ratingas the predictive score for the event candidate based upon the extentthe server identifies the pattern match between the event candidate andthe portion of the context data related to the first ID node.

In still another embodiment, method 4300 may have step 4310 generatingthe predictive score for the event candidate by having the servercompare the event candidate to at least a portion of the context datarelated to the first ID node, and then determine a probability rank asthe predictive score for the event candidate based upon the comparisonbetween the event candidate and the portion of the context data relatedto the first ID node.

At step 4315, method 4300 proceeds with the server updating nodemanagement information based upon a type of the event candidate and thepredictive score for the event candidate. As previously noted, exemplarynode management information may be generally implemented as nodemanagement data (e.g., context data 560) and/or node management rules(e.g., rule data 3610) related to one or more of the node elements inthe wireless node network. Thus, in a particular embodiment of method4300, the node management information may comprise node management datamaintained by the server where the node management data relates to oneor more ID nodes within the wireless node network and includes contextdata (such as data 560 or data within databased 565) maintained by theserver. Further embodiments may have the node management informationcomprising node management data maintained by the server and relating tothe master node; a node management rule maintained by the server anddefining one or more parameters of an operational profile for one ormore ID nodes within the wireless node network; a node management rulemaintained by the server and defining one or more parameters of anoperational profile for the master node; a node management rule definingone or more parameters on how the master node identifies the eventcandidate; and a node management rule defining one or more parameters onhow the master node simplifies a data feed between the master node andthe server.

In still another embodiment of step 4315, method 4300 may implement theupdating step with the server transforming the node managementinformation to further indicate a correspondence between the noderelevant activity and the updated status related to the first ID node.Such a transformation may be based upon the type of the event candidateand the predictive score for the event candidate. Stated another way,the transformed node management information may be updated, revised,changed, or otherwise altered to better account for the reported eventcandidate as measured with the predictive score or confidence ranking.

At step 4320, method 4300 proceeds with the server transmitting amanagement message to the master node where the management messageprovides at least a portion of the updated node management informationto the master node as feedback to the master node. Such feedback is thenused for enhanced management of one or more elements of the wirelessnode network. In a further embodiment of method 4300, the transmittingstep may involve the server providing the portion of the updated nodemanagement information to the master node as management control inputfor the master node that alters how the master node operates or altershow the master node manages at least one of the ID nodes. In moredetail, the portion of the updated node management information providedas the control input may include an updated node management rulerefining how the master node identifies the event candidate, which mayrefine how the master node simplifies a data feed between the masternode and the server (as previously discussed).

Those skilled in the art will appreciate that method 4300 as disclosedand explained above in various embodiments may be implemented on anexemplary master node (e.g., exemplary server 3400 in FIGS. 34 and 36)running one or more parts of the server control and management code 525in conjunction with event candidate analytics engine code 3405 toperform steps of method 4300 as described above. Such code may be storedon a non-transitory computer-readable medium, such as memory storage 515on server 3400. Thus, when executing such code, the server may bespecially adapted to interact with other network devices (such asdirectly with master node 3410 as shown in FIG. 34 and indirectly withone or more ID nodes as shown in FIG. 34 via messages, commands, andinstructions issued directly to master node 3410 as shown in FIG. 34) asthe server's processing unit 500 is specially adapted to be operative toperform algorithmic operations or steps from the exemplary methodsdisclosed above, including method 4300 and variations of that method.

FIG. 44 is a flow diagram illustrating another exemplary method forenhanced management of a wireless node network based upon receipt of andprocessing of an event candidate in accordance with another embodimentof the invention. Referring now to FIG. 44, method 4400 begins at step4405 where the server receives an event candidate identified by themaster node. The event candidate is related to a first of the ID nodesand represents an updated status related to the first ID node. Such anupdated status may comprise a changed status of the first ID node, anunchanged status of the first ID node, or a summarized checkpoint statusof the first ID node in further embodiments of method 4400.

At step 4410, method 4400 proceeds with the server ranking the eventcandidate for confidence of representing a node relevant activity basedupon context data maintained by the server and related to the first IDnode. In more detail, the step of ranking the event candidate mayinvolve generating a predictive score based upon an evaluation of theevent candidate against at least a portion of the context data relatedto the first ID node for confidence of representing the node relevantactivity. Generally, node relevant activity may be activity having animpact on or relevant to node operations. For example, the node relevantactivity may be an anticipated activity characterized by at least aportion of the context data related to the first ID node. In anotherexample, the node relevant activity may be a new activity not presentlycharacterized by a current state of the context data identified to berelated to the first ID node.

At step 4415, method 4400 proceeds with the server revising nodemanagement information based upon a type of the event candidate and theranking of the event candidate. Such node management information ismaintained by the server and is related to at least one of the masternode and the first ID node. More specifically, exemplary node managementinformation may comprise at least one of (a) node management datamaintained by the server that is related to one or more ID nodes withinthe wireless node network and where the node management data includesthe context data maintained by the server and related to the first IDnode; (b) node management data maintained by the server and related tothe master node; (c) a node management rule maintained by the server anddefining one or more parameters of an operational profile for one ormore ID nodes within the wireless node network; (d) a node managementrule maintained by the server and defining one or more parameters of anoperational profile for the master node; (e) a node management ruledefining one or more parameters on how the master node identifies theevent candidate; and (f) a node management rule defining one or moreparameters on how the master node simplifies a data feed between themaster node and the server.

In a further embodiment of method 4400, the revising step may furthercomprise having the server transform the node management information tofurther indicate a correspondence between the node relevant activity andthe updated status related to the first ID node. Such a transformationis based upon the type of the event candidate and the ranking of theevent candidate. Examples of such node relevant activity may furtherinclude at least one of movement of at least one of the first ID node,the master node, and an object near the master node; exposure to asource of shielding that inhibits communication between the first IDnode and the master node; exposure to a source of RF interference; andplacement of the first ID node within a container.

At step 4420, method 4400 proceeds with the server transmitting amanagement message to the master node. The management message providesat least a portion of the revised node management information to themaster node as instructional input to be used by the master node. Suchinstructional input may be used by the master node to control anoperation of the master node or alter how the master node operates. Inother examples, the instructional input may be used by the master nodeto cause at least one of the ID nodes to alter operation or alters howthe master node manages at least one of the ID nodes. In more detail,the instructional input may include an updated node management ruledefining how the master node identifies the event candidate or refininghow the master node simplifies a data feed between the master node andthe server.

Those skilled in the art will appreciate that method 4300 as disclosedand explained above in various embodiments may be implemented on anexemplary master node (e.g., exemplary server 3400 in FIGS. 34 and 36)running one or more parts of the server control and management code 525in conjunction with event candidate analytics engine code 3405 toperform steps of method 4300 as described above. Such code may be storedon a non-transitory computer-readable medium, such as memory storage 515on server 3400. Thus, when executing such code, the server may bespecially adapted to interact with other network devices (such asdirectly with master node 3410 as shown in FIG. 34 and indirectly withone or more ID nodes as shown in FIG. 34 via messages, commands, andinstructions issued directly to master node 3410 as shown in FIG. 34) asthe server's processing unit 500 is specially adapted to be operative toperform algorithmic operations or steps from the exemplary methodsdisclosed above, including method 4300 and variations of that method.

In another apparatus embodiment, a further exemplary server apparatusfor enhanced management of a wireless node network is described asfollows. The network has at least a plurality of ID nodes and a masternode in communication with the ID nodes. The server node apparatus inthis embodiment generally comprises a server processing unit, a memorystorage, a timer, and a network communication interface (e.g., such asexemplary server 3400 and the internal exemplary circuit components ofthis server apparatus as shown and described with respect to FIGS. 5 and36). In more detail, the memory storage is coupled to the serverprocessing unit and maintains at least event candidate analytics enginecode, and node management information used to control one or more of theID nodes and the master node as part of managing the wireless nodenetwork. The node management information stored on the memory storageincludes at least context data describing a contextual environment ofthe ID nodes and rule data used for node control operations. The nodemanagement information stored on the memory storage includes at leastcontext data describing a contextual environment of the ID nodes ormaster node (e.g., sources of anticipated RF interference or noise in ananticipated physical environment to be encountered by the ID nodes orthe master node) and rule data used for node control operations. Forexample, the rule data may define at least one parameter of anoperational profile (e.g., a power profile, alert profile, etc.) for oneor more ID nodes within the wireless node network; may define one ormore parameters on how the master node identifies the event candidate;or may define one or more parameters on how the master node simplifies adata feed coupling the master node and network interface of the serverapparatus.

The network interface, like the memory storage, is coupled to the serverprocessing unit, such as shown and described relative to FIGS. 5 and 36relative to exemplary network interface 590. The network interface isoperative to communicate with the master node over a networkcommunication path, which allows the server to directly interact withthe master node but does not allow the server to directly interact withthe ID nodes. Instead, the server is able to indirectly interact withthe ID nodes through the master node (acting as an intermediary that maypass along information or control input to one or more of the ID nodes).

When executing the event candidate analytics engine code maintained onthe memory storage, the server processing unit in the server apparatusbecomes the core of a specially adapted device and, thus, operative tointeract with other elements of the wireless node network in novel andunconventional ways while providing enhanced management of the networkin response to receiving an event candidate. In particular, the serverprocessing unit, as adapted under the executing code stored in thememory storage, is operative to receive, via the network interface, anevent candidate from the master node where the event candidate isidentified by the master node as representing an updated status relatedto the first ID node. The updated status may comprise, in some furtherembodiments, a changed status of the first ID node, an unchanged statusof the first ID node, or a summarized checkpoint status of the first IDnode.

The server processing unit is then operative to generate a confidencerating for the event candidate based upon an evaluation of the eventcandidate against at least a portion of the context data (where theconfidence rating indicates a degree to which the event candidaterepresents a node relevant activity). Such node relevant activity may bean anticipated activity characterized by at least a portion of thecontext data related to the first ID node or a new activity notcharacterized by a current state of the context data identified to berelated to the first ID node. The node relevant activity may alsocomprise at least one of a detectable physical activity and a detectableelectromagnetic activity. Further examples of node relevant activity mayinclude movement of at least one of the first ID node, the master node,and an object near the master node; exposure to a source of shieldingthat inhibits communication between the first ID node and the masternode; exposure to a source of RF interference; and placement of thefirst ID node within a container.

The server processing unit is also operative to update the nodemanagement information stored on the memory storage based upon a type ofthe event candidate and the confidence rating for the event candidate.To update the node management information, the server may, in a moredetailed embodiment, be operative to transform the node managementinformation to further indicate a correspondence between the noderelevant activity and the updated status related to the first ID node.More specifically, the server processing unit may be operative totransform the node management information based upon the type of theevent candidate and the confidence rating of the event candidate.

The server processing unit is also operative to cause the networkinterface to transmit a management message to the master node where themanagement message provides at least a portion of the updated nodemanagement information to the master node as instructional input to beused by the master node. In a further embodiment, the instructionalinput is used by the master node to cause at least one of the ID nodesto alter operation. In another embodiment, the instructional input mayused by the master node to control an operation of the master node,alter how the master node operates, or alter how the master node managesat least one of the ID nodes. In other embodiments, the instructionalinput may comprise updated rule data defining how the master nodeidentifies the event candidate or refine how the master node simplifiesa data fee between the master node and the server.

Other embodiments may further leverage such an exemplary serverapparatus as part of a system embodiment. For example, an embodiment ofan enhanced node management system for a wireless node network having aplurality of ID nodes is described as follows. The system generallycomprises a master node and a server in communication with the masternode as part of the wireless node network. The master node is disposedas an element within the wireless node network that executes an eventdetection engine code to become operative to generate a report message.The report message transmits information regarding an event candidaterepresenting an updated status related to a first of the ID nodes (suchas a changed status of the first ID node, an unchanged status of thefirst ID node, or a summarized checkpoint status of the first ID node).The master node is also operated as part of the system to receive amanagement message from the server as a type of feedback in response tothe generated report message. Such a management message, as describedbelow, may include instructional or control input for the master node asthe server learns and adaptively issues instructional feedback inresponse to the generated report message in order to enhance and improvehow the system manages the network.

The server communicates with the master node over a first communicationpath, such as a network 105 as shown in FIG. 34. The server maintainsnode management information used to control one or more of the ID nodesand the master node as part of managing the wireless node network. Suchnode management information generally includes at least context datadescribing a contextual operating environment of the ID nodes and ruledata used for node control operations of the ID nodes and the masternode. In more detail, the rule data (also logically referred to as oneor more node management rules) may define at least one parameter of anoperational profile for one or more ID nodes and/or at least oneparameter of an operational profile for the master node.

As the server executes an event candidate analytics engine codemaintained on the server, the server becomes specially adapted toprovide novel and unconventional operations as part of the systemembodiment relative to how the system provides enhanced management ofelements in the wireless node network. More specifically, when executingthe event candidate analytics engine code, the server is operative tofirst receive the report message from the master node and extract theevent candidate from the report message. The event candidate in thereport message has been previously identified by the master node asrepresenting the updated status related to the first ID node.

The server is further operative, as part of this system embodiment, togenerate a confidence rating for the event candidate based upon anevaluation of the event candidate compared to at least a portion of thecontext data maintained by the server. The confidence rating indicates adegree to which the event candidate represents a node relevant activity.As previously noted, exemplary node relevant activity may comprise atleast one of a detectable physical activity and a detectableelectromagnetic activity. In another embodiment, the node relevantactivity may be an anticipated activity characterized by at least aportion of the context data that is related to the first ID node.Further still, the node relevant activity may a new activity notcharacterized by the context data identified as related to the first IDnode (such as when the confidence rating is below minimal pointindicating the event candidate represents new node relevant activitypreviously uncharacterized by the system). In still more detail,exemplary node relevant activity may comprise node related movement(such as movement the first ID node, the master node, and/or an objectnear the master node); exposure to a source of shielding that inhibitscommunication between the first ID node and the master node (such as thenode being placed next to structure that shields or otherwise reduceselectromagnetic communications with the node); exposure to a source ofRF interference (such as the node being near a motor that emitsundesired electromagnetic interference to hinders or impairscommunications with the node); and placement of the first ID node withina container (such as placement of an ID node within a metal ULD that nolonger permits the ID node to communicate directly with an externalmaster node).

The server is also operative, as part of this system embodiment, toupdate the node management information based upon a type of the eventcandidate and the confidence rating for the event candidate. As such,the server is the component of the system that essentially “learns” fromthe reported event candidate so that the server can provide quicker andmore efficient management of components within the wireless nodenetwork. In a further embodiment, the server may update the nodemanagement information by transforming the node management informationto further indicate a correspondence between the node relevant activityand the updated status related to the first ID node. In more detail, theserver may transform the node management information based upon the typeof the event candidate and the confidence rating of the event candidate.

The server in this system embodiment is further operative to transmitthe management message to the master node (which is received by themaster node in the system as discussed above). The management messageprovides at least a portion of the updated node management informationto the master node as instructional input to be used by the master node.In a more detailed embodiment, the instructional input may used by themaster node to control an operation of the master node, such as causingthe master node to alter how the master node operates. In anotherembodiment, the instructional input from the server to the master nodemay have the master node cause at least one of the ID nodes to alteroperation or, in even more detail, to cause the master node to send asecond management message to at least one of the ID nodes where thesecond management message causes the one of the ID nodes to alter howthe one of the ID nodes operates. For example, the portion of therevised node management information provided as the instructional inputmay comprise updated rule data (such as a new or revised node managementrule or profile used by a node during operation).

A more detailed system embodiment for enhanced management of a wirelessnode network having a plurality of ID nodes is described as followswhere the system handles multiple event candidates. The system generallycomprises a server and a master node disposed within the wireless nodenetwork. The master node (such as master node 3410) is in communicationwith the server (such as server 3400) over a first communication path(such as network 105) in communication with the ID nodes (such as IDnodes 120 a-120 e) over a second communication path distinct from thefirst communication path.

The master node maintains first engine code (such as event detectionengine code 3415) that may be executed on the master node to speciallyadapt the master node so that the master node becomes operative toprovide, in conjunction with certain functionality of the server, noveland unconventional operations as part of this collective systemembodiment. In particular, when the master node executes the firstengine code, the master node becomes operative to detect a first updatedstatus related to a first of the ID nodes (where the detected firststatus is represented by a first event candidate); detect a secondupdated status related to a second of the ID nodes (where the detectedsecond status is represented by a second event candidate); transmit thefirst event candidate and the second event candidate to the server overthe first communication path; and receive a management message inresponse after transmitting the first event candidate and the secondevent candidate to the server.

In this particular systems embodiment, the server maintains nodemanagement information used to control one or more of the ID nodes andthe master node as part of managing the wireless node network. Such nodemanagement information comprises at least context data describing acontextual operating environment of the ID nodes and rule data used fornode control operations of the ID nodes and the master node.

The server also maintains second engine code (such as event candidateanalytics engine code 3400) that may be executed on the server so thatthe server becomes specially adapted and operative to provide, inconjunction with the above described functionality of the master node inthis embodiment, novel and unconventional operations as part of thiscollective system embodiment. In more detail, when the server executesthe second engine code, the server becomes operative to first receivethe first event candidate and the second event candidate from the masternode. The server is further operative to generate a first confidencerating for the first event candidate based upon an evaluation of thefirst event candidate compared to at least a first portion of thecontext data maintained by the server. The first confidence ratingindicates a degree to which the first event candidate represents a noderelevant activity. The server is also operative to generate a secondconfidence rating for the second event candidate based upon anevaluation of the second event candidate compared to at least a secondportion of the context data maintained by the server, where the secondconfidence rating indicates a degree to which the second event candidaterepresents the node relevant activity.

The server is further operative to compare the first confidence ratingand the second confidence rating to determine a combined confidencerating reflecting a degree to which the detected first change and thedetected second change represent a pattern corresponding to the samenode relevant activity; update the node management information basedupon a type of the first event candidate, a type of the second eventcandidate, and the combined confidence rating; and then transmit themanagement message to the master node. Such a management messageprovides at least a portion of the updated node management informationto the master node as instructional input to be used by the master node(e.g., updated context data describing a contextual operatingenvironment of the ID nodes and/or updated rule data used for nodecontrol operations of the ID nodes and the master node).

Further Particular Embodiments

What follows below is a listing of exemplary sets of particularembodiments focusing on one or more aspects of the different embodimentsdescribed above. Each of the different sets for their respectiveparticular embodiments effect improvements to the technology of improvedand enhanced monitoring for node-specific event candidates related toelements of a wireless node network and managing components within thenetwork based upon reported event candidates. These help improve overalloperation of the network from improving the efficiency of how to monitorthe wireless node network and how to responsively and actively managedifferent elements of the network in a learning mode. As such, withineach further embodiment heading are numbered aspects describing aspecific technological application of one or more nodes in such awireless node network that improve or otherwise enhance these technicalfields, as explicitly explained and supported by the disclosure above.Each numbered aspect appearing below a particular heading may makereference to other numbered aspects that appear below that particularheading in a dependent relationship.

Further Embodiment A—Systems, Apparatus, and Methods of Event Monitoringfor an Event Candidate Related to an ID Node within a Wireless NodeNetwork

1. A method for enhanced monitoring for an event candidate within awireless node network having a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node, comprising the steps of: receiving, by the master node, afirst advertising signal broadcast by a first of the ID nodes;receiving, by the master node, a second advertising signal broadcast bythe first ID node after the first ID node broadcasts the firstadvertising signal; identifying, by the master node, the event candidatebased upon a comparison of an observed parameter of the firstadvertising signal and the second advertising signal; and reporting, bythe master node to the server, the event candidate relative to the firstID node.

2. The method of embodiment 1, wherein the reporting step furthercomprises simplifying, by the master node, a data feed about the firstID node by sending the event candidate to the server as summaryinformation reflecting an observed change between the first advertisingsignal and the second advertising signal.

3. The method of embodiment 1, wherein the identifying step furthercomprises identifying, by the master node, a pattern between at leastthe first advertising signal and the second advertising signal basedupon the observed parameter, wherein the pattern reflecting summarizedinformation related to the first ID node as the event candidate.

4. The method of embodiment 1, wherein the observed parameter comprisesan observed signal strength value as detected by the master node.

5. The method of embodiment 1, wherein the identifying step furthercomprises identifying, by the master node, an observed pattern betweenat least a first signal strength value of the first advertising signaland a second signal strength value of the second advertising signal,wherein the observed pattern reflecting summarized information relatedto the first ID node as the event candidate.

6. The method of embodiment 5, wherein the event candidate reported tothe server avoids the need to update the server with information on allsignals received by the master node from the first ID node.

7. The method of embodiment 1, wherein the step of identifying the eventcandidate comprises comparing the observed parameter of the secondadvertising signal to an average of the observed parameters of a set ofprior advertising signals from the first ID node including the firstadvertising signal.

8. The method of embodiment 1, wherein the observed parameter comprisesa received signal strength indicator (RSSI) reflecting a signal strengthas detected by the master node; and wherein the step of identifying theevent candidate comprises comparing a received signal strength indicatorvalue of the second advertising signal to an average of a set ofreceived signal strength indicator values of advertising signals fromthe first ID node broadcast prior to the second advertising signal.

9. The method of embodiment 8, wherein the averaged set of receivedsignal strength indicator values of advertising signals from the firstID node broadcast prior to the second advertising signal comprises amoving average of the set of received signal strength indicator valuesof advertising signals from the first ID node broadcast within a movingwindow prior to the second advertising signal.

10. The method of embodiment 4, wherein the observed parameter comprisesa shift in the observed signal strength value as received by the masternode; and wherein the step of identifying the event candidate furthercomprises: detecting the shift in received signal strength value whencomparing the first advertising signal and the second advertisingsignal; and identifying the event candidate as a shift event when thedetected shift in received signal strength value is at least a thresholdvalue.

11. The method of embodiment 4, wherein the observed parameter comprisesan observed shift in the signal strength value as received by the masternode; and wherein the step of identifying the event candidate andreporting the event candidate to the server further comprises: detectinga beginning shift in received signal strength value when the observedshift in the signal strength value between the received firstadvertising signal compared to the received second advertising signal isat least an initiating threshold value; receiving, by the master node, asubsequent advertising signal broadcast by the first ID node after thefirst ID node broadcasts the second advertising signal; detecting acontinued shift in received signal strength value when the observedshift in the signal strength value between the received secondadvertising signal compared to the received subsequent advertisingsignal; and reporting, by the master node to the server, the eventcandidate as a shift event only after detecting the beginning shift andif the detected continued shift is less than a continued event thresholdvalue.

12. The method of embodiment 11, wherein the reporting step comprisesdelaying transmission of the event candidate to the server by the masternode until the detected continued shift based upon the observed signalstrength value of the subsequent advertising signal is less than thecontinued event threshold value.

13. The method of embodiment 1, wherein the observed parameter comprisesa detected time between successive advertising signals broadcast fromthe first ID node and as received by the master node.

14. The method of embodiment 13, wherein the step of identifying theevent candidate comprises: detecting a time gap between the firstadvertising signal and the second advertising signal as the observedparameter; and identifying the event candidate when the detected timegap is less than a threshold time gap.

15. The method of embodiment 14, wherein the step of identifying theevent candidate further comprises identifying the event candidate as anonline event when the detected time gap is less than the threshold timegap and the master node receives at least one additional advertisingsignal broadcast by the first ID node within the threshold time gapafter the second advertising signal.

16. The method of embodiment 15, wherein the step of identifying theevent candidate as the online event occurs when (a) the detected timegap between the first advertising signal and the second advertisingsignal is less than the threshold time gap and (b) the master node hasreceived at least a threshold number of advertising signals from thefirst ID node each of which are received by the master node within thethreshold time gap from each other, wherein receipt of the firstadvertising signal and receipt of the second advertising signal areincluded in the threshold number of advertising signals received fromthe first ID node.

17. The method of embodiment 13, wherein the step of identifying theevent candidate comprises identifying the event candidate as an offlineevent when (a) the detected time since the master node received thesecond advertising signal is greater than a threshold time gap and (b)the master node previously identified an online event related to signalsfrom the first ID node including the first advertising signal and thesecond advertising signal.

18. The method of embodiment 1, wherein the step of identifying theevent candidate further comprises identifying the event candidate as asporadic event when the master node receives at least the firstadvertising signal and the second advertising signal but does notreceive at least a threshold number of advertising signals from thefirst ID node within a defined period of time from when the master nodereceives the first advertising signal.

19. The method of embodiment 1, wherein the step of identifying theevent candidate further comprises identifying the event candidate as acheckpoint event when a periodic reporting interval ends and based uponthe comparison of the observed parameter of the first advertising signaland the second advertising signal.

20. The method of embodiment 19 further comprising: detecting, by themaster node, an alert flag from the first ID node, the alert flag beingpart of at least one of the first advertising signal and the secondadvertising signal; and reducing the periodic reporting interval whenthe master node detects the alert flag.

21. The method of embodiment 20, wherein periodic reporting intervalcomprises a time period adjustable by the master node.

22. The method of embodiment 20, wherein periodic reporting intervalcomprises a number of signal receptions adjustable by the master node.

23. The method of embodiment 20, wherein the alert flag comprises aprofile identifier indicating an alert profile being used by the firstID node, the alert profile for the first ID node being one of aplurality of operational profiles that govern advertising signalbroadcasting operations by the first ID node.

24. The method of embodiment 19 further comprising resetting informationcollected based upon the first advertising signal and the secondadvertising signal after reporting the checkpoint event to the server bythe master node for data reduction purposes on the master node.

25. The method of embodiment 1, wherein the observed parameter comprisesan observed profile setting; and wherein the step of identifying theevent candidate further comprises identifying the event candidate as aprofile change event when the comparison indicates the observed profilesetting of the second advertising signal is different than the observedprofile setting of the first advertising signal.

26. The method of embodiment 25, wherein the observed profile settingrelates to operation of the first ID node.

27. The method of embodiment 25, wherein the observed profile settingrelates to operation of the master node.

28. The method of embodiment 1, wherein the observed parameter comprisesan observed output power setting for the first ID node; and wherein thestep of identifying the event candidate further comprises identifyingthe event candidate as a transmission power change event when thecomparison indicates the observed output power setting related to thesecond advertising signal is different than the observed output powersetting related to the first advertising signal.

29. The method of embodiment 1, wherein the observed parameter comprisessensor data gathered by a sensor on the first ID node; and wherein thestep of identifying the event candidate further comprises identifyingthe event candidate as an environmental change event when the comparisonindicates a second sensor data value included as part of the secondadvertising signal is different than a first sensor data value includedas part of the first advertising signal.

30. The method of embodiment 1, wherein the observed parameter comprisessensor data gathered by at least one sensor on the first ID node; andwherein the step of identifying the event candidate further comprisesidentifying the event candidate as an environmental change event whenthe comparison indicates a second sensor data value included as part ofthe second advertising signal reflects a departure from a first sensordata value included as part of the first advertising signal, wherein thedeparture is more than a threshold difference.

31. The method of embodiment 1 further comprising receiving, by themaster node, an adjustment response from the server based upon the eventcandidate.

32. The method of embodiment 31, wherein the adjustment responsecomprises an adjusted profile for at least one of the master node andthe first ID node.

33. The method of embodiment 32, wherein the adjustment responsecomprises an adjusted profile for at least one of the other ID nodes.

34. The method of embodiment 31, wherein the adjustment responsecomprises updated context data reflecting the reported event candidate.

35. The method of embodiment 1 further comprising the steps of:receiving, by the master node, a third advertising signal broadcast bythe first ID node after the first ID node broadcasts the secondadvertising signal; receiving, by the master node, a fourth advertisingsignal broadcast by the first ID node after the first ID node broadcaststhe third advertising signal; generating, by the master node, a firstcheckpoint summary as a statistical representation of the firstadvertising signal and the second advertising signal; generating, by themaster node, a second checkpoint summary as a statistical representationof the third advertising signal and the fourth advertising signal; andwherein the step of identifying the event candidate comprisesidentifying, by the master node, the event candidate based upon acomparison of an observed parameter for each of the first checkpointsummary and the second checkpoint summary.

36. A method for enhanced monitoring for an event candidate within awireless node network having a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node, comprising the steps of: detecting, by the master node, aplurality of advertising signals broadcast by a first of the ID nodesover a time period; identifying, by the master node, the event candidaterelative to the first ID node when an observed parameter of theadvertising signals changes over the time period to reflect the eventcandidate; and reporting, by the master node to the server, the eventcandidate relative to the first ID node.

37. The method of embodiment 36, wherein the reporting step furthercomprises reducing, by the master node, data obtained by the master nodeabout the first ID node by sending the event candidate to the server assummary information reflecting an observed change between theadvertising signals.

38. The method of embodiment 36, wherein the observed parameter of theadvertising signals comprises a summarized observed pattern between theadvertising signals.

39. The method of embodiment 36, wherein the observed parametercomprises an observed signal strength value as detected by the masternode.

40. The method of embodiment 39, wherein the event candidate reported tothe server avoids the need to update the server with information aboutthe signal strength value of each of the advertising signals received bythe master node from the first ID node.

41. The method of embodiment 36, wherein the step of identifying theevent candidate comprises comparing the observed parameter of a mostrecently detected one of the advertising signals to a moving average ofthe observed parameter of the previously detected ones of theadvertising signals to identify the event candidate.

42. The method of embodiment 36, wherein the observed parametercomprises a received signal strength indicator (RSSI) reflecting asignal strength as detected by the master node; and wherein the step ofidentifying the event candidate comprises comparing a received signalstrength indicator value of a most recently detected one of theadvertising signals to a moving average of the received signal strengthindicator values of the prior advertising signals within a prior movingwindow to identify the event candidate.

43. The method of embodiment 39, wherein the observed parametercomprises a shift in signal strength as detected by the master node; andwherein the step of identifying the event candidate further comprisesidentifying the event candidate as a shift event when the detected shiftin the signal strength value for each of the advertising signals exceedsa threshold value.

44. The method of embodiment 39, wherein the observed parametercomprises an observed shift in the signal strength value as received bythe master node; and wherein the step of identifying the event candidateand reporting the event candidate to the server further comprises:detecting a beginning shift in received signal strength value when theobserved shift in the signal strength value between the plurality ofadvertising signals is at least an initiating threshold value;receiving, by the master node, at least one subsequent advertisingsignal broadcast by the first ID node after the first ID node broadcaststhe plurality of advertising signals; detecting a continued shift inreceived signal strength value when the observed shift in the signalstrength value between a last of the received plurality of advertisingsignals compared to the received subsequent advertising signal; andreporting, by the master node to the server, the event candidate as ashift event only after detecting the beginning shift and if the detectedcontinued shift is less than a continued event threshold value.

45. The method of embodiment 36, wherein the step of identifying theevent candidate further comprises identifying the event candidate as anonline event when the master node has received at least a thresholdnumber of the advertising signals from the first ID node within athreshold time gap between successive ones of the advertising signals.

46. The method of embodiment 36, wherein the step of identifying theevent candidate further comprises identifying the event candidate as anoffline event when (a) an elapsed time since the master node received alast of the advertising signals is greater than a threshold time gap and(b) the master node previously identified an online event related to atleast a portion of the advertising signals from the first ID node.

47. The method of embodiment 36, wherein the step of identifying theevent candidate further comprises identifying the event candidate as anoffline event when the master node has received at least a first of theadvertising signals but not a threshold number of successive ones of theadvertising signals within a defined period of time from when the masternode receives the first advertising signal.

48. The method of embodiment 36, wherein the step of identifying theevent candidate further comprises identifying the event candidate as acheckpoint event when the time period ends and the master node detectsat least one additional advertising signals broadcast by the first IDnode.

49. The method of embodiment 48 further comprising: detecting, by themaster node, an alert flag from the first ID node, the alert flag beingpart of at least one of the plurality of advertising signals; andreducing the time period when the master node detects the alert flag.

50. The method of embodiment 49, wherein the alert flag comprises aprofile identifier indicating an alert profile being used by the firstID node, the alert profile for the first ID node being one of aplurality of operational profiles that govern advertising signalbroadcasting operations by the first ID node.

51. The method of embodiment 36, wherein the observed parametercomprises an observed profile setting; and wherein the step ofidentifying the event candidate further comprises identifying the eventcandidate as a profile change event when the observed profile setting ofthe advertising signals changes from a first setting to a second settingover the time period.

52. The method of embodiment 51, wherein the observed profile settingrelates to operation of the first ID node.

53. The method of embodiment 51, wherein the observed profile settingrelates to operation of the master node.

54. The method of embodiment 36, wherein the step of identifying theevent candidate further comprises identifying the event candidate as atransmission power change event when the observed parameter comprises anobserved output power setting for the first ID node.

55. The method of embodiment 36, wherein the step of identifying theevent candidate further comprises identifying the event candidate as anenvironmental change event when the observed parameter comprises sensordata gathered by a sensor on the first ID node.

56. The method of embodiment 36 further comprising receiving, by themaster node, an adjustment response from the server based upon the eventcandidate.

57. The method of embodiment 56, wherein the adjustment responsecomprises an adjusted profile for at least one of the master node andthe first ID node.

58. The method of embodiment 57, wherein the adjustment responsecomprises an adjusted profile for at least one of the other ID nodes.

59. The method of embodiment 56, wherein the adjustment responsecomprises updated context data reflecting the reported event candidate.

60. The method of embodiment 36, wherein the detecting step comprisesdetecting, by the master node, a first set of advertising signalsbroadcast by the first ID node and a second set of advertising signalsbroadcast by the first ID node after the first set of advertisingsignals, the first set of advertising signals and the second set ofadvertising signals being part of the plurality of advertising signals;and wherein the identifying step comprises: generating, by the masternode, a first checkpoint summary as a statistical representation of thefirst set of advertising signals; generating, by the master node, asecond checkpoint summary as a statistical representation of the secondset of advertising signals; and identifying, by the master node, theevent candidate based upon a comparison of an observed parameter foreach of the first checkpoint summary and the second checkpoint summary.

86. A master node apparatus for enhanced monitoring for an eventcandidate within a wireless node network having a plurality of ID nodesand a server, the master node apparatus comprising: a node processingunit; a memory storage coupled to the node processing unit, the memorystorage maintaining event detection engine code for execution by thenode processing unit; a first communication interface coupled to thenode processing unit and operative to communicate with at least a firstof the ID nodes over a first communication path; a second communicationinterface coupled to the node processing unit and operative tocommunicate with the server over a second communication path; andwherein the node processing unit, when executing the event detectionengine code maintained on the memory storage, is operative to: detect,via the first communication interface, a first advertising signalbroadcast by the first ID node over the first communication path,detect, via the first communication interface, a second advertisingsignal broadcast by the first ID node over the first communication pathafter the first ID node broadcasts the first advertising signal, comparean observed parameter of each of the first advertising signal and thesecond advertising signal, identify the event candidate based upon thecomparison of the observed parameter of each of the first advertisingsignal and the second advertising signal, and cause the secondcommunication interface to report the identified event candidate to theserver over the second communication path.

87. The master node apparatus of embodiment 86, wherein the secondcommunication interface is operative to transmit a message to the serverwhen reporting the identified event candidate, the message reflectingthe identified event candidate as reduced monitoring overhead for thefirst ID node on the second communication path.

88. The master node apparatus of embodiment 87, wherein the messagereflecting the identified event candidate comprises summary informationreflecting an observed change between the first advertising signal andthe second advertising signal.

89. The master node apparatus of embodiment 86, wherein the observedparameter comprises a signal strength value as detected by the nodeprocessing unit via the first communication interface.

90. The master node apparatus of embodiment 88, wherein the observedchange comprises a shift in observed signal strength value between atleast a first signal strength value of the first advertising signal anda second signal strength value of the second advertising signal, whereinthe change reflecting summarized information related to the first IDnode as the event candidate.

91. The master node apparatus of embodiment 86, wherein the nodeprocessing unit is operative to compare the observed parameter of eachof the first advertising signal and the second advertising signal bybeing further operative to compare the observed parameter of the secondadvertising signal to an average of the observed parameters of a set ofprior advertising signals from the first ID node including the firstadvertising signal.

92. The master node apparatus of embodiment 86, wherein the observedparameter comprises a received signal strength indicator as detected bythe node processing unit; and wherein the node processing unit isoperative to compare the observed parameter of each of the firstadvertising signal and the second advertising signal by being furtheroperative to compare a received signal strength indicator value of thesecond advertising signal to an average of a set of received signalstrength indicator values of prior advertising signals from the first IDnode including the first advertising signal.

93. The master node apparatus of embodiment 92, wherein the averaged setof received signal strength indicator values of advertising signals fromthe first ID node broadcast prior to the second advertising signalcomprises a moving average of the set of received signal strengthindicator values of advertising signals from the first ID node broadcastwithin a window prior to the second advertising signal.

94. The master node apparatus of embodiment 89, wherein the nodeprocessing unit is operative to identify the event candidate by beingfurther operative to: detect a shift in received signal strength valuewhen comparing the signal strength value of first advertising signal andthe signal strength value of the second advertising signal; and identifythe event candidate as a shift event when the detected shift in receivedsignal strength value is at least a threshold value.

95. The master node apparatus of embodiment 89, wherein the observedparameter comprises an observed shift in the signal strength value asdetected by the node processing unit; and wherein the node processingunit is operative to identify the event candidate and cause the secondcommunication interface to report the event candidate to the server bybeing further operative to: detect a beginning shift in received signalstrength value when the observed shift in the signal strength valuebetween the plurality of advertising signals is at least an initiatingthreshold value; detect, via the first communication interface, at leastone subsequent advertising signal broadcast by the first ID node afterthe first ID node broadcasts the second advertising signal; detect, viathe first communication interface, a continued shift in received signalstrength value when the observed shift in the signal strength valuebetween the second advertising signal compared to the receivedsubsequent advertising signal; and cause the second communicationinterface to report the event candidate to the server as a shift eventonly after detecting the beginning shift and if the detected continuedshift is less than a continued event threshold value.

96. The master node apparatus of embodiment 86, wherein the observedparameter comprises a time between successive advertising signalsbroadcast from the first ID node and as detected by the node processingunit via the first communication interface.

97. The master node apparatus of embodiment 96, wherein the nodeprocessing unit is operative to identify the event candidate by beingfurther operative to detect a time gap between the first advertisingsignal and the second advertising signal and identify the eventcandidate when the detected time gap is less than a threshold time gap.

98. The master node apparatus of embodiment 97, wherein the nodeprocessing unit is operative to identify the event candidate as anonline event when the detected time gap is less than the threshold timegap and the first communication interface detects at least oneadditional advertising signal broadcast by the first ID node within thethreshold time gap after the second advertising signal.

99. The master node apparatus of embodiment 98, wherein the nodeprocessing unit is operative to identify the event candidate as theonline event when (a) the detected time gap between the firstadvertising signal and the second advertising signal is less than thethreshold time gap and (b) the first communication interface hasdetected at least a threshold number of advertising signals from thefirst ID node each of which are detected by the first communicationinterface within the threshold time gap from each other, whereindetection of the first advertising signal and detection of the secondadvertising signal are included in the threshold number of advertisingsignals from the first ID node.

100. The master node apparatus of embodiment 86, wherein the nodeprocessing unit is operative to identify the event candidate as anoffline event when (a) the detected time since the first communicationinterface detected the second advertising signal is greater than athreshold time gap and (b) the node processing unit previouslyidentified an online event related to signals from the first ID nodeincluding the first advertising signal and the second advertisingsignal.

101. The master node apparatus of embodiment 86, wherein the nodeprocessing unit is operative to identify the event candidate as asporadic event when the first communication interface detects at leastthe first advertising signal and the second advertising signal but doesnot detect at least a threshold number of advertising signals from thefirst ID node within a defined period of time from when the firstcommunication interface detects the first advertising signal.

102. The master node apparatus of embodiment 86, wherein the nodeprocessing unit is operative to identify the event candidate as acheckpoint event when a periodic reporting interval ends and based uponthe comparison of the observed parameter of the first advertising signaland the second advertising signal.

103. The master node apparatus of embodiment 102, wherein the nodeprocessing unit is further operative to: detect an alert flag from thefirst ID node, the alert flag being part of a header for at least one ofthe first advertising signal and the second advertising signal; andreduce the periodic reporting interval upon detecting the alert flag.

104. The master node apparatus of embodiment 103, wherein periodicreporting interval comprises a time period adjustable by the nodeprocessing unit.

105. The master node apparatus of embodiment 103, wherein periodicreporting interval comprises a number of signal receptions adjustable bythe node processing unit.

106. The master node apparatus of embodiment 103, wherein the alert flagcomprises a profile identifier indicating an alert profile being used bythe first ID node, the alert profile for the first ID node being one ofa plurality of operational profiles that govern advertising signalbroadcasting operations by the first ID node.

107. The master node apparatus of embodiment 86, wherein the nodeprocessing unit is further operative to delete gathered signalinformation stored on the memory storage after causing the secondcommunication interface to report the checkpoint event to the server,the gathered signal information having been collected from the firstadvertising signal and from the second advertising signal and previouslystored on the memory storage after detection.

108. The master node apparatus of embodiment 86, wherein the observedparameter comprises an observed profile setting; and wherein the nodeprocessing unit is operative to identify the event candidate as aprofile change event when the comparison indicates the observed profilesetting of the second advertising signal is different than the observedprofile setting of the first advertising signal.

109. The master node apparatus of embodiment 86, wherein the observedparameter comprises an observed output power setting for the first IDnode; and wherein the node processing unit is operative to identify theevent candidate as a transmission power change event when the comparisonby the node processing unit indicates the observed output power settingrelated to the second advertising signal is different than the observedoutput power setting related to the first advertising signal.

110. The master node apparatus of embodiment 86, wherein the observedparameter comprises sensor data gathered by a sensor on the first IDnode; and wherein the node processing unit is operative to identify theevent candidate as an environmental change event when the comparison bythe node processing unit indicates a second sensor data value includedas part of the second advertising signal differs more than a thresholdamount when compared to a first sensor data value included as part ofthe first advertising signal.

111. The master node apparatus of embodiment 86, wherein the nodeprocessing unit is further operative to receive, via the secondcommunication interface, an adjustment response from the server basedupon the event candidate.

112. The master node apparatus of embodiment 111, wherein the adjustmentresponse comprises an adjusted profile for at least one of the masternode apparatus and the first ID node.

113. The master node apparatus of embodiment 112, wherein the adjustmentresponse comprises an adjusted profile for at least one of the other IDnodes.

114. The master node apparatus of embodiment 111, wherein the adjustmentresponse comprises updated context data reflecting the reported eventcandidate, wherein the updated context data is used by the nodeprocessing unit when managing the ID nodes.

115. The master node apparatus of embodiment 86, wherein the nodeprocessing unit is further operative to: detect, via the firstcommunication interface, a third advertising signal broadcast by thefirst ID node over the first communication path after the first ID nodebroadcasts the second advertising signal; detect, via the firstcommunication interface, a fourth advertising signal broadcast by thefirst ID node over the first communication path after the first ID nodebroadcasts the third advertising signal; generate a first checkpointsummary as a statistical representation of the first advertising signaland the second advertising signal; generate a second checkpoint summaryas a statistical representation of the third advertising signal and thefourth advertising signal; compare the observed parameter for each ofthe first checkpoint summary and the second checkpoint summary; andwherein the node processing unit is operative to identify the eventcandidate based upon the comparison of the observed parameter for eachof the first checkpoint summary and the second checkpoint summary.

116. A monitoring system that identifies an event candidate within awireless node network, the system comprising: a server disposed at a toplevel within the wireless node network; an ID node disposed at a lowlevel within the wireless node network; a master node disposed at amiddle level within the wireless node network, wherein the master nodefurther comprises a master node processing unit, a second memory storagecoupled to the master node processing unit, the memory storagemaintaining event detection engine code for execution by the master nodeprocessing unit, a first communication interface coupled to the masternode processing unit and operative to communicate with the ID node overa first communication path, and a second communication interface coupledto the master node processing unit and operative to communicate with theserver over a second communication path, wherein the first communicationpath is different from the second communication path; wherein the masternode, when executing the event detection engine code on the master nodeprocessing unit, is operative to detect, with the first communicationinterface, a first advertising signal broadcast by the ID node over thefirst communication path, detect, with the first communicationinterface, a second advertising signal broadcast by the ID node over thefirst communication path after the ID node broadcasts the firstadvertising signal, compare an observed parameter of each of the firstadvertising signal and the second advertising signal, identify the eventcandidate based upon the comparison of the observed parameter of each ofthe first advertising signal and the second advertising signal, andcause the second communication interface to report the identified eventcandidate to the server over the second communication path.

117. The system of embodiment 116, wherein the second communicationinterface of the master node is operative to transmit a message to theserver when reporting the identified event candidate, the messagecomprising summary information reflecting a monitored change relative tothe ID node.

118. The system of embodiment 116, wherein the observed parametercomprises a signal strength value as detected by the master node via thefirst communication interface.

119. The system of embodiment 116, wherein the observed parametercomprises a signal strength value as detected by the master node via thefirst communication interface; and wherein the monitored changecomprises a shift in signal strength value between at least a firstsignal strength value of the first advertising signal and a secondsignal strength value of the second advertising signal.

120. The system of embodiment 116, wherein the master node processingunit is operative to compare the observed parameter of each of the firstadvertising signal and the second advertising signal by being furtheroperative to compare the observed parameter of the second advertisingsignal to an average of the observed parameters of a set of prioradvertising signals from the ID node including the first advertisingsignal.

121. The system of embodiment 116, wherein the observed parametercomprises a received signal strength indicator (RSSI) reflecting asignal strength as detected by the master node; and wherein the masternode processing unit is operative to compare the parameter of each ofthe first advertising signal and the second advertising signal by beingfurther operative to compare a received signal strength indicator valueof the second advertising signal to an average of a set of receivedsignal strength indicator values of prior advertising signals from theID node including the first advertising signal.

122. The system of embodiment 121, wherein the averaged set of receivedsignal strength indicator values of advertising signals from the ID nodebroadcast prior to the second advertising signal comprises a movingaverage of the set of received signal strength indicator values ofadvertising signals from the ID node broadcast within a moving windowprior to the second advertising signal.

123. The system of embodiment 118, wherein the observed parametercomprises a shift in the received signal strength value as detected bythe master node; and wherein the master node processing unit isoperative to identify the event candidate by being further operative to:detect the shift in received signal strength value when comparing thesignal strength value of first advertising signal and the signalstrength value of the second advertising signal; and identify the eventcandidate as a shift event when the detected shift in received signalstrength value is at least a threshold value.

124. The system of embodiment 118, wherein the observed parametercomprises an observed shift in the signal strength value as detected bythe master node; and wherein the master node is operative to identifythe event candidate and cause reporting of the event candidate to theserver by being further operative to: detect a beginning shift inreceived signal strength value when the observed shift in the signalstrength value between the detected first advertising signal compared tothe detected second advertising signal is at least an initiatingthreshold value; detect a subsequent advertising signal broadcast by thefirst ID node after the first ID node broadcasts the second advertisingsignal; identify a continued shift in received signal strength valuewhen the observed shift in the signal strength value between thereceived second advertising signal compared to the received subsequentadvertising signal; and cause the second communication interface toreport the event candidate to the server as a shift event only afterdetecting the beginning shift and if the identified continued shift isless than a continued event threshold value.

125. The system of embodiment 116, wherein the observed parametercomprises a detected time between successive advertising signalsbroadcast from the ID node and as detected by the master node.

126. The system of embodiment 125, wherein the master node processingunit is operative to identify the event candidate by being furtheroperative to detect a time gap between the first advertising signal andthe second advertising signal as the observed parameter; and identifythe event candidate when the detected time gap is less than a thresholdtime gap.

127. The system of embodiment 126, wherein the master node processingunit is operative to identify the event candidate as an online eventwhen the detected time gap is less than the threshold time gap and thefirst communication interface of the master node detects at least oneadditional advertising signal broadcast by the ID node within thethreshold time gap after the second advertising signal.

128. The system of embodiment 127, wherein the master node processingunit is operative to identify the event candidate as the online eventwhen (a) the detected time gap between the first advertising signal andthe second advertising signal is less than the threshold time gap and(b) the first communication interface of the master node has detected atleast a threshold number of advertising signals from the ID node each ofwhich are received by the master node within the threshold time gap fromeach other, wherein detection of the first advertising signal anddetection of the second advertising signal are included in the thresholdnumber of advertising signals from the ID node.

129. The system of embodiment 125, wherein the master node processingunit is operative to identify the event candidate as an offline eventwhen (a) the detected time since the first communication interfacedetected the second advertising signal is greater than a threshold timegap and (b) the master node processing unit previously identified anonline event related to signals from the ID node including the firstadvertising signal and the second advertising signal.

130. The system of embodiment 116, wherein the master node processingunit is operative to identify the event candidate as a sporadic eventwhen the first communication interface detects at least the firstadvertising signal and the second advertising signal but does not detectat least a threshold number of advertising signals from the ID nodewithin a defined period of time from when the master node detects thefirst advertising signal.

131. The system of embodiment 116, wherein the master node processingunit is operative to identify the event candidate as a checkpoint eventwhen a periodic reporting interval ends and based upon the comparison ofthe observed parameter of the first advertising signal and the secondadvertising signal.

132. The system of embodiment 131, wherein the master node is furtheroperative to: detect an alert flag from the first ID node, the alertflag being part of at least one of the detected first advertising signaland the detected second advertising signal; and reduce the periodicreporting interval when the master node detects the alert flag.

133. The system of embodiment 132, wherein periodic reporting intervalcomprises a time period adjustable by the master node.

134. The system of embodiment 132, wherein periodic reporting intervalcomprises a number of signal receptions adjustable by the master node.

135. The system of embodiment 132, wherein the alert flag comprises aprofile identifier indicating an alert profile being used by the firstID node, the alert profile for the first ID node being one of aplurality of operational profiles that govern advertising signalbroadcasting operations by the first ID node.

136. The system of embodiment 131, wherein the master node processingunit is further operative to delete gathered signal information storedon the memory storage after causing the second communication interfaceto report the checkpoint event to the server as the identified eventcandidate, the gathered signal information having been collected fromthe first advertising signal and from the second advertising signal andpreviously stored on the memory storage after detection.

137. The system of embodiment 116, wherein the observed parametercomprises an observed profile setting; and wherein the master nodeprocessing unit is operative to identify the event candidate as aprofile change event when the comparison indicates the observed profilesetting of the second advertising signal is different than the observedprofile setting of the first advertising signal.

138. The system of embodiment 116, wherein the observed parametercomprises an observed output power setting for the first ID node; andwherein the master node processing unit is operative to identify theevent candidate as a transmission power change event when the comparisonby the node processing unit indicates the observed output power settingrelated to the second advertising signal is different than the observedoutput power setting related to the first advertising signal.

139. The system of embodiment 116, wherein the ID node further comprisesa sensor operative to sense environmental data relative to a vicinity ofthe ID node and provide the environmental data to the master node assensor data relative to the ID node, the sensor data collected over timebeing included in the first advertising signal and the secondadvertising signal; wherein the observed parameter comprises the sensordata collected by the sensor on the first ID node; and wherein themaster node processing unit is operative to identify the event candidateas an environmental change event when the comparison by the master nodeprocessing unit indicates a second value of the sensor data included aspart of the second advertising signal differs more than a thresholdamount when compared to a first value of the sensor data included aspart of the first advertising signal.

140. The system of embodiment 116, wherein the server is furtheroperative to receive the event candidate from the master node, adjustnode management information resident on the server based upon the eventcandidate, generate an adjustment response consistent with the adjustednode management information, and transmit the adjustment response to themaster node.

141. The system of embodiment 140, wherein the master node processingunit is further operative to receive, via the second communicationinterface, the adjustment response from the server.

142. The system of embodiment 141, wherein the adjustment responsecomprises an adjusted profile for at least one of the master nodeapparatus and the ID node.

143. The system of embodiment 142, wherein the adjustment responsecomprises an adjusted profile for a second ID node operative tocommunicate with the master node.

144. The system of embodiment 141, wherein the adjustment responsecomprises updated context data reflecting the reported event candidate,wherein the updated context data is used by the master node processingunit when managing the ID node.

145. The system of embodiment 116, wherein the master node is furtheroperative to: detect, with the first communication interface, a thirdadvertising signal broadcast by the ID node over the first communicationpath after the ID node broadcasts the second advertising signal; detect,with the first communication interface, a fourth advertising signalbroadcast by the ID node over the first communication path after the IDnode broadcasts the third advertising signal; generate a firstcheckpoint summary as a statistical representation of the firstadvertising signal and the second advertising signal; generate a secondcheckpoint summary as a statistical representation of the thirdadvertising signal and the fourth advertising signal; compare theobserved parameter for each of the first checkpoint summary and thesecond checkpoint summary; and wherein the master node is furtheroperative to identify the event candidate based upon the comparison ofthe observed parameter for each of the first checkpoint summary and thesecond checkpoint summary.

Further Embodiment B—Systems, Apparatus, and Methods of Event Monitoringfor an Event Candidate within a Wireless Node Network Based UponSighting Events, Sporadic Events, and Benchmark Checkpoint Events

147. A method for enhanced monitoring for an event candidate within awireless node network having a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node, comprising the steps of: (a) detecting, by the master node,a first signal broadcast by a first of the ID nodes; (b) identifying, bythe master node, the event candidate as a first sighting event relatedto the first ID node when the master node detects the first signal; (c)generating, by the master node, event data representing the firstsighting event once the master node identifies the first sighting event,wherein the event data representing the first sighting event comprisesan identifier of the first ID node and further comprises at least timinginformation and observed signal strength information characterizing thefirst sighting event; (d) reporting, by the master node, the event datarepresenting the first sighting event to the server upon generating theevent data representing the first sighting event; (e) identifying, bythe master node, the event candidate as a sporadic event related to thefirst ID node when (1) the master node has not identified a firstbenchmark checkpoint event related to the first ID node and (2) themaster node has not detected a subsequent signal broadcast by the firstID node within a gap time period from when the master node detected amost recent signal from the first ID node; (f) generating, by the masternode, event data representing the sporadic event if the master nodeidentifies the sporadic event, wherein the event data representing thesporadic event comprises at least timing information and observed signalstrength information characterizing the sporadic event; (g) reporting,by the master node, the event data representing the sporadic event tothe server upon generating the event data representing the sporadicevent; (h) determining, by the master node, a first average of anobserved signal strength value for an initial number of subsequentsuccessive signals broadcast from the first ID node and detected by themaster node including the first signal as long as an elapsed timebetween each of the initial number of subsequent successive signals isless than the gap time; (i) identifying, by the master node, the eventcandidate as a first benchmark checkpoint event based upon the firstaverage of observed signal strength value, the first benchmarkcheckpoint event representing a detected online state of the first IDnode by the master node; (j) generating, by the master node, event datarepresenting the first benchmark checkpoint event once the master nodeidentifies the first benchmark checkpoint event, wherein the event datarepresenting the first benchmark checkpoint event comprises at leasttiming information and observed signal strength informationcharacterizing the first benchmark checkpoint event; and (k) reporting,by the master node, the event data representing the first benchmarkcheckpoint event to the server upon generating the event datarepresenting the first benchmark checkpoint event.

148. The method of embodiment 147 further comprising the steps of: (1)identifying, by the master node, the event candidate as an offline eventrelated to the first ID node when (1) the master node previouslyidentified the first benchmark checkpoint event related to the first IDnode and (2) the master node fails to detect a subsequent signalbroadcast by the first ID node within the gap time period from when themaster node detected a most recent of the subsequent successive signalsfrom the first ID node; (m) generating, by the master node, event datarepresenting the offline event once the master node identifies theoffline event, wherein the event data representing the offline eventcomprises at least timing information and observed signal strengthinformation characterizing the offline event; (n) reporting, by themaster node, the event data representing the offline event to the serverupon generating the event data representing the offline event.

149. The method of embodiment 147 further comprising the steps of: (o)identifying, by the master node, a new checkpoint event related to thefirst ID node when the master node determines a subsequent thresholdnumber of moving averages of the observed signal strength value afterthe first benchmark checkpoint event; (p) detecting, by the master node,if a difference between the moving average of the observed signalstrength value associated with the new checkpoint event and the movingaverage of the observed signal strength value associated with a previousbenchmark checkpoint event at or above a threshold observed signalstrength difference value; (q) identifying, by the master node, theevent candidate as a shift event related to the first ID node when thedetected difference in step (p) is at or above the threshold observedsignal strength difference value; (r) generating, by the master node,event data representing the shift event related to the first ID nodeonce the master node identifies the shift event, wherein the event datarepresenting the shift event comprises at least timing information andobserved signal strength information characterizing the shift event; and(s) reporting, by the master node, the event data representing the shiftevent to the server upon generating the event data representing theshift event.

150. The method of embodiment 147 further comprising the steps of: (t)identifying, by the master node, the event candidate as a new summarycheckpoint event when the master node has successfully identified athreshold number of successive new checkpoint events; (u) generating, bythe master node, event data representing the new summary checkpointevent after the master node successfully identified the threshold numberof successive new checkpoint events, wherein the event data representingthe new summary checkpoint event comprises at least timing informationand observed signal strength information characterizing the new summarycheckpoint event; and (v) reporting, by the master node, the event datarepresenting the new summary checkpoint event to the server upongenerating the event data representing the new summary checkpoint event.

151. The method of embodiment 147 further comprising the step ofreplacing event data representing the previous benchmark checkpointevent with the event data representing the new checkpoint eventsubsequent to step (p).

152. The method of embodiment 150 further comprising the step ofreplacing event data representing the previous benchmark checkpointevent with the event data representing the new summary checkpoint eventsubsequent to step (v).

153. The method of embodiment 147, wherein the event data for an eventassociated with the first ID node comprises information originallyprovided by the first ID node to the master node, the informationfurther comprising at least a current battery voltage of the first IDnode, a temperature value associated with the first ID node, and payloaddata provided by the first ID node.

154. The method of embodiment 147, wherein the timing information andobserved signal strength information characterizing the first sightingevent further comprises one or more from the group comprising atimestamp identifying when the master node detected the first signal andthe observed signal strength value for the first signal.

155. The method of embodiment 147, wherein the timing information andobserved signal strength information characterizing the sporadic eventcomprises one or more from the group comprising a timestamp on when themaster node identified the sporadic event, an average of observed signalstrength value for any signals broadcast by the first ID node anddetected by the master node from the first signal and before the gaptime period elapsed, and a count of the signals broadcast by the firstID node and detected by the master node from the first signal and beforethe gap time period elapsed.

156. The method of embodiment 147, wherein the timing information andobserved signal strength information characterizing the first benchmarkcheckpoint event as an online event comprises one or more from the groupcomprising a timestamp on when the master node identified the firstbenchmark checkpoint event, the moving average of observed signalstrength value at the first benchmark checkpoint event, and a count ofthe signals broadcast by the first ID node and detected by the masternode between the identified first sighting event and the identifiedfirst benchmark checkpoint event.

157. The method of embodiment 148, wherein the timing information andobserved signal strength information characterizing the offline eventcomprises one or more from the group comprising a timestamp on when themaster node identified the offline event, the moving average of observedsignal strength value between a most recent benchmark checkpoint eventand when the master node identified the offline event, and a count ofthe signals broadcast by the first ID node and detected by the masternode between the most recent benchmark checkpoint event and when themaster node identified the offline event.

158. The method of embodiment 149, wherein the timing information andobserved signal strength information characterizing the shift eventcomprises one or more from the group comprising a timestamp on when themaster node identified the shift event, the moving average of observedsignal strength value between a most recent benchmark checkpoint eventand when the master node identified the shift event, and a count of thesignals broadcast by the first ID node and detected by the master nodebetween the most recent benchmark checkpoint event and when the masternode identified the shift event.

159. The method of embodiment 150, wherein the timing information andobserved signal strength information characterizing the new summarycheckpoint event comprises a timestamp on when the master nodeidentified the new summary checkpoint event, the moving average ofobserved signal strength value between a most recent benchmarkcheckpoint event and when the master node identified the new summarycheckpoint event, and a count of the signals broadcast by the first IDnode and detected by the master node between the most recent benchmarkcheckpoint event and when the master node identified the new summarycheckpoint event.

160. The method of embodiment 147 further comprising: detecting, by themaster node, an alert flag reflecting a status of the first ID node, thealert flag being part of the first signal; and increasing how frequentlythe master node updates the server with reports related to the first IDnode if the master node detects the alert flag is set.

161. The method of embodiment 160, wherein the increasing step comprisesdecreasing, by the master node, the threshold number of detected signalsfrom the first ID node needed to qualify as a checkpoint event if themaster node detects the alert flag is set.

162. The method of embodiment 160, wherein the increasing step comprisesdecreasing, by the master node, the threshold number of previouscheckpoint events needed for the master node to report the event datarepresenting the new checkpoint event if the master node detects thealert flag is set.

163. The method of embodiment 160, wherein the alert flag comprises aprofile identifier indicating an alert profile being used by the firstID node, the alert profile for the first ID node being one of aplurality of operational profiles that govern advertising signalbroadcasting operations by the first ID node.

164. The method of embodiment 147 further comprising the steps of:identifying, by the master node, the event candidate as a profile changeevent related to the first ID node when the master node observes analtered profile setting of the first ID node as reflected in thesubsequent successive signals broadcast from the first ID node;generating, by the master node, event data representing the profilechange event once the master node identifies the profile change event,wherein the event data representing the profile change event comprisesat least timing information and observed profile setting informationcharacterizing the profile change event; and reporting, by the masternode, the event data representing the profile change event to the serverupon generating the event data representing the profile change event.

165. The method of embodiment 147 further comprising the steps of:identifying, by the master node, the event candidate as a profile changeevent related to the master node when the master node alters a profilesetting of master node; generating, by the master node, event datarepresenting the profile change event once the master node identifiesthe profile change event, wherein the event data representing theprofile change event comprises at least timing information and observedprofile setting information characterizing the profile change event; andreporting, by the master node, the event data representing the profilechange event to the server upon generating the event data representingthe profile change event.

166. A master node apparatus for enhanced monitoring for an eventcandidate within a wireless node network having a plurality of ID nodesand a server, the master node apparatus comprising: a node processingunit; a memory storage coupled to the node processing unit, the memorystorage maintaining event detection engine code for execution by thenode processing unit; a timer coupled to the node processing unit andoperative to track an elapsed time after an initiating event; a firstcommunication interface coupled to the node processing unit andoperative to communicate with at least a first of the ID nodes over afirst communication path; a second communication interface coupled tothe node processing unit and operative to communicate with the serverover a second communication path; and

wherein the node processing unit, when executing the event detectionengine code maintained on the memory storage, is operative to detect,via the first communication interface, a first signal broadcast by afirst of the ID nodes over the first communication path, identify theevent candidate as a first sighting event related to the first ID nodewhen the master node detects the first signal, generate event datarepresenting the first sighting event after identifying the firstsighting event, wherein the event data representing the first sightingevent comprises an identifier of the first ID node and further comprisesat least timing information and observed signal strength informationcharacterizing the first sighting event, cause the second communicationinterface to provide the event data representing the first sightingevent to the server, monitor, via the first communication interface, forany in a series of successive signals broadcast by the first ID nodewithin an event horizon for the first ID node after detecting the firstsignal, track, via the timer, the elapsed time between successive onesof the first signal and any in the series of successive signalsbroadcast by the first ID node, track a received signal strengthindicator value for the first signal and any in the series of successivesignals broadcast by the first ID node, identify the event candidate asa subsequent event related to the first node and within the eventhorizon beginning with the first sighting event, the subsequent eventbeing identified based upon timing information related to the elapsedtime tracked by the timer and based upon observed signal strengthinformation as indicated by the received signal strength indicatorvalue, generate event data representing the subsequent event asincluding at least the timing information related to the elapsed timetracked by the timer and based upon observed signal strength informationas indicated by the received signal strength indicator value, and causethe second communication interface to provide the event datarepresenting the subsequent event to the server.

167. The master node apparatus of embodiment 166, wherein the subsequentevent comprises a sporadic event when: (1) the node processing unit hasnot identified a previous event within the event horizon to be a firstbenchmark checkpoint event representing detection of a threshold numberof the signals within the series of successive signals broadcast by thefirst ID node; and (2) the node processing unit has not detected, viathe first communication interface, a subsequent signal broadcast by thefirst ID node before the elapsed time exceeds a gap time period whentracked by the time from when the master node detected a most recent inthe series of successive signals from the first ID node.

168. The master node apparatus of embodiment 166, wherein the subsequentevent comprises a first benchmark checkpoint event representing adetected online state of the first ID node when the node processing unitdetects, via the first communication interface, a threshold number ofthe signals within the series of successive signals broadcast by thefirst ID node and without the elapsed time between each of the thresholdnumber of detected signals does not exceed a gap time period.

169. The master node apparatus of embodiment 166, wherein the subsequentevent comprises an offline event when: (1) the node processing unitidentified a previous event within the event horizon to be a firstbenchmark checkpoint event representing detection of a threshold numberof the signals within the series of successive signals broadcast by thefirst ID node; and (2) the node processing unit has not detected asubsequent signal broadcast by the first ID node when the elapsed timefrom when a most recent of the signals in the series of successivesignals from the first ID node exceeds a gap time period.

170. The master node apparatus of embodiment 166, wherein the subsequentevent comprises a new checkpoint event when: (1) the node processingunit has identified a previous event within the event horizon to be afirst benchmark checkpoint event, wherein the first benchmark checkpointevent representing detection of an earlier threshold number of thesignals within the series of successive signals broadcast by the firstID node; and (2) the node processing unit detects a subsequent thresholdnumber of the signals in the series of successive signals from the firstID node after identifying the first benchmark checkpoint event.

171. The master node apparatus of embodiment 170, wherein the nodeprocessing unit is further operative to generate the event datarepresenting the subsequent event and cause the second communicationinterface to provide the event data representing the subsequent event tothe server by being further operative to: generate the event datarepresenting the new checkpoint event upon identifying a thresholdnumber of previous checkpoint events; and cause the second communicationinterface to provide the event data representing the new checkpointevent to the server after identifying the threshold number of previouscheckpoint events.

172. The master node apparatus of embodiment 166, wherein the subsequentevent comprises a shift event when the node processing unit is furtheroperative to detect at least a threshold difference between the receivedsignal strength indicator value for the new checkpoint event and thereceived signal strength indicator value for a previous benchmarkcheckpoint event.

Further Embodiment C—Systems, Apparatus, and Methods of Time Gap RelatedMonitoring for an Event Candidate Related to an ID Node within aWireless Node Network

61. A method for enhanced monitoring for an event candidate within awireless node network having a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node, comprising the steps of: scanning, by the master node, fora first of the ID nodes; receiving, by the master node, a plurality ofsignals from the first ID node; detecting a plurality of time gapsbetween successive ones of the signals as the master node receives eachof the signals; comparing each of the signals to identify a change in anobserved parameter of each of the signals; identifying, by the masternode, the event candidate when at least one of the identified change inthe observed parameter and the detected time gaps matches an eventcriteria; and reporting, by the master node to the server, the eventcandidate relative to the first ID node.

62. The method of embodiment 61, wherein the reporting step furthercomprises reducing, by the master node, data obtained by the master nodeabout the first ID node from the plurality of signals by sending theevent candidate to the server as summary information reflecting thechange in the parameter of the signals over time.

63. The method of embodiment 61, wherein the change in the observedparameter of the signals comprises a detected shift between the signalsbased upon the observed parameter over time.

64. The method of embodiment 63, wherein the observed parametercomprises an observed signal strength value as detected by the masternode.

65. The method of embodiment 64, wherein the event candidate reported tothe server avoids the need to update the server with information aboutthe signal strength value of each of the signals received by the masternode from the first ID node.

66. The method of embodiment 61, wherein the observed parametercomprises a received signal strength indicator (RSSI) reflecting asignal strength as detected by the master node; and wherein thecomparing step comprises comparing a received signal strength indicatorvalue of a most recently received one of the signals to a moving averageof the received signal strength indicator values of a rolling window ofthe previously received ones of the signals to identify the eventcandidate.

67. The method of embodiment 64, wherein the event candidate comprises ashift event when the event criteria comprises a condition met when (a)the master node identifies the change in the observed parameter of thesignals over time as reflecting a shift in the observed signal strengthvalue for the signals over time and (b) the shift exceeds a thresholdvalue.

68. The method of embodiment 64, wherein the observed parametercomprises an observed shift in the signal strength value as received bythe master node; and wherein the step of identifying the event candidateand reporting the event candidate to the server further comprises:detecting a beginning shift in received signal strength value when theobserved shift in the signal strength value between the receivedplurality of signals is at least an initiating threshold value;receiving, by the master node, at least one subsequent signal broadcastby the first ID node after the first ID node broadcasts the receivedplurality of signals; detecting a continued shift in received signalstrength value when the observed shift in the signal strength valuebetween a last of the received plurality of signals compared to thereceived subsequent signal; and reporting, by the master node to theserver, the event candidate as a shift event only after detecting thebeginning shift and if the detected continued shift is less than acontinued event threshold value.

69. The method of embodiment 61, wherein the event candidate comprisesan online event when the event criteria comprises a condition met when(a) the master node has received at least a threshold number ofsuccessive ones of the signals from the first node and (b) the detectedtime gaps between the successive ones of the signals do not exceed athreshold time gap.

70. The method of embodiment 61, wherein the event candidate comprisesan offline event when the event criteria comprises a condition met when(a) an elapsed time since the master node received a last of the signalsis greater than a threshold time gap and (b) the master node previouslyidentified an online event related to the rest of the signals receivedby the master node from the first ID node.

71. The method of embodiment 61, wherein the event candidate comprises asporadic event when the event criteria comprises a condition met whenthe master node has received at least a first of the signals but not athreshold number of successive ones of the signals within a definedperiod of time from when the master node detects the first signal.

72. The method of embodiment 61, wherein the event candidate comprises acheckpoint event when the event criteria comprises a condition met whena periodic reporting interval ends and the master node detects at leastone additional signal broadcast by the first ID node.

73. The method of embodiment 72 further comprising: detecting, by themaster node, an alert flag reflecting a status of the first ID node, thealert flag being part of at least one of the received plurality ofsignals; and reducing the periodic reporting interval when the masternode detects the alert flag.

74. The method of embodiment 73, wherein periodic reporting intervalcomprises a time period adjustable by the master node.

75. The method of embodiment 73, wherein periodic reporting intervalcomprises a number of signal receptions adjustable by the master node.

76. The method of embodiment 73, wherein the alert flag comprises aprofile identifier indicating an alert profile being used by the firstID node, the alert profile for the first ID node being one of aplurality of operational profiles that govern advertising signalbroadcasting operations by the first ID node.

77. The method of embodiment 72 further comprising resetting informationcollected by the master node based upon the signals after reporting thecheckpoint event as the event candidate to the server to conserve use ofmemory on the master node.

78. The method of embodiment 61 further comprising: identifying aprofile change event when the master node detects a changed profilesetting of the signals over time; and reporting, by the master node tothe server, the profile change event relative to the first ID node.

79. The method of embodiment 61 further comprising identifying atransmission power change event when the master node detects a changedtransmission power setting of the signals over time; and reporting, bythe master node to the server, the transmission power change eventrelative to the first ID node.

80. The method of embodiment 61 further comprising: identifying anenvironmental change event when the master node detects a change insensor data gathered from the first ID node via the signals over time;and reporting, by the master node to the server, the environmentalchange event relative to the first ID node.

81. The method of embodiment 61 further comprising receiving, by themaster node, an adjustment response from the server based upon the eventcandidate.

82. The method of embodiment 81, wherein the adjustment responsecomprises an adjusted profile for at least one of the master node andthe first ID node.

83. The method of embodiment 82, wherein the adjustment responsecomprises an adjusted profile for at least one of the other ID nodes.

84. The method of embodiment 81, wherein the adjustment responsecomprises updated context data reflecting the reported event candidate.

85. The method of embodiment 61, wherein the receiving step comprisesreceiving, by the master node, a first set of advertising signalsbroadcast by the first ID node and a second set of advertising signalsbroadcast by the first ID node after the first set of advertisingsignals, the first set of advertising signals and the second set ofadvertising signals being part of the plurality of signals received bythe master node from the first ID node; further comprising the steps of:generating, by the master node, a first checkpoint summary as astatistical representation of the first set of advertising signals;generating, by the master node, a second checkpoint summary as astatistical representation of the second set of advertising signals; andwherein the comparing step comprises comparing an observed parameter foreach of the first checkpoint summary and the second checkpoint summaryto identify the change.

Further Embodiment D—Systems, Apparatus, and Methods of EnhancedMonitoring for an Event Candidate Associated with Cycling Power of an IDNode within a Wireless Node Network

146. A method for enhanced monitoring for an event candidate within awireless node network having a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node, comprising the steps of: receiving, by the master node, afirst plurality of advertising signals broadcast by a first of the IDnodes; detecting, by the master node, if the first ID node isbroadcasting with a cycling broadcast RF power profile setting basedupon at least one of the first plurality of advertising signals, thecycling broadcast RF power profile setting defining a cycle period overwhich the first ID node alters how it broadcasts at different RF powerlevels; receiving, by the master node, a second plurality of advertisingsignals broadcast by the first ID node after the first ID nodebroadcasts the first plurality of advertising signals, wherein thesecond plurality of advertising signals are broadcast with the cyclingbroadcast RF power profile setting; determining, by the master node, afirst average of an observed parameter for the first plurality ofadvertising signals within a first window of time commensurate with thecycle period; determining, by the master node, a second average of theobserved parameter for the second plurality of advertising signalswithin a second window of time commensurate with the cycle period;identifying, by the master node, the event candidate when a comparisonof the first average and the second average indicates an observed changerelative to the first ID node; and reporting, by the master node to theserver, the event candidate relative to the first ID node.

Additional embodiments may include a master node programmed to beoperative or configured to perform the steps from embodiment 146 recitedabove. Additionally, a system embodiment may include such a programmedmaster node and the first ID node as described above. Still further,another system may include a server, the programmed master node, and thefirst ID node described in the embodiment of 146 as interacting in amanner that provide for monitoring with respect to the cycling broadcastRF power profile setting for the ID node.

Further Embodiment E—Systems, Apparatus, and Methods of EnhancedCheckpoint Summary Based Monitoring for an Event Candidate Related to anID Node within a Wireless Node Network

239. A method for enhanced monitoring for an event candidate within awireless node network having a plurality of ID nodes, a master node incommunication with the ID nodes, and a server in communication with themaster node, comprising the steps of: activating, by the master node, amonitoring mode of operation that listens for one or more broadcastsignals emitted from any of the ID nodes without prompting the ID nodesfor transmission of the one or more broadcast signals from the ID nodes;receiving, by the master node, a first advertising signal broadcast by afirst of the ID nodes; recording, by the master node, an observedparameter related to the received first advertising signal broadcast bythe first ID node; successively receiving, by the master node, asubsequent group of advertising signals broadcast by the first ID node;recording, by the master node, the observed parameter related to each ofthe successively received subsequent group of advertising signalsbroadcast by the first ID node; generating, by the master node, a firstcheckpoint summary representing a first set of advertising signalscomprising the received first advertising signal and the successivelyreceived subsequent group of advertising signals, the first checkpointsummary comprising a summary observed parameter generated based upon therecorded observed parameter related to the received first advertisingsignal broadcast and the recorded observed parameter related to each ofthe successively received subsequent group of advertising signals; andtransmitting, by the master node, the first checkpoint summary to theserver as the event candidate relative to the first ID node.

240. The method of embodiment 239, wherein the transmitting step furthercomprises simplifying, by the master node, a data feed for the serverrelated to a status of the first ID node by sending the event candidateto the server indicating a summarized monitored status of the first nodebased upon the summary observed parameter of the first checkpointsummary.

241. The method of embodiment 239, wherein the summary observedparameter for the first checkpoint summary comprises a statisticalrepresentation of the observed signal strength values for the first setof advertising signals.

242. The method of embodiment 241, wherein the statisticalrepresentation of the observed signal strength values comprises one froma group consisting of a mean, a median, an average, a moving averageover a subset window of advertising signals, a moving average over asliding time window, or a weighted average.

243. The method of embodiment 239, wherein each of the observedparameter related to the received first advertising signal and theobserved parameter related to each of the successively receivedsubsequent group of advertising signals comprises a received signalstrength indicator (RSSI) value reflecting a signal strength as detectedby the master node.

244. The method of embodiment 239, wherein each of the observedparameter related to the received first advertising signal and theobserved parameter related to each of the successively receivedsubsequent group of advertising signals comprises one of a plurality ofsensor data captured by the master node related to the first ID node.

245. The method of embodiment 239, wherein the transmitting step furthercomprises transmitting, by the master node, the first checkpoint summaryto the server as the event candidate relative to the first ID node whenthe first checkpoint summary meets a periodic reporting intervalcriteria relative to one or more prior checkpoint summaries generated bythe master node.

246. The method of embodiment 245, wherein the transmitting step furthercomprises: incrementing, by the master node, a checkpoint count inmemory of the master node upon generating the first checkpoint summary;comparing, by the master node, the incremented checkpoint count to theperiodic reporting interval criteria relative to one or more priorcheckpoint summaries generated by the master node; and reporting, by themaster node, the first checkpoint summary to the server as the eventcandidate when the incremented checkpoint count matches the periodicreporting interval criteria.

247. The method of embodiment 246, wherein the periodic reportinginterval criteria identifies a threshold number of generated checkpointsummaries as a reporting condition for reporting the first checkpointsummary to the server as the event candidate.

248. The method of embodiment 245 further comprising: detecting, by themaster node, a profile identifier from the first ID node, the profileidentifier being part of at least one of the received first advertisingsignal and the successively received subsequent group of advertisingsignals; and altering, by the master node, the periodic reportinginterval criteria based upon an alert profile corresponding to theprofile identifier, the alert profile comprising a plurality of nodemanagement rules related to monitoring the first ID node and reportingto the server.

249. The method of embodiment 246 further comprising adjusting, by themaster node, the summary observed parameter reported to the server aspart of the event candidate to statistically summarize the firstcheckpoint summary with at least one previous checkpoint summarygenerated by the master node and not reported to the server.

250. The method of embodiment 239 further comprising comparing aprevious summary observed parameter for a previous checkpoint summary tothe summary observed parameter for the first checkpoint summary toidentify a change in a status of the first ID node; and transmitting thefirst checkpoint summary to the server as the event candidate when thecomparison identifies the change in the status of the first ID node.

251. The method of embodiment 250, wherein the change in the status ofthe first ID node comprises when the previous summary observed parameterfor the previous checkpoint summary is different than the summaryobserved parameter for the first checkpoint summary by more than athreshold level.

252. The method of embodiment 250, wherein the change in the status ofthe first ID node identifies the first checkpoint summary as at leastone node event from the group consisting of a sporadic event indicatingan abbreviated event horizon for the first ID node, an online eventindicating a beginning of a monitored event horizon for the first IDnode, a shift event indicating at least a threshold difference betweenthe previous summary observed parameter for the previous checkpointsummary and the summary observed parameter for the first checkpointsummary, and an offline event indicating an end of the monitored eventhorizon for the first ID node.

253. The method of embodiment 250, wherein the change in the status ofthe first ID node identifies the first checkpoint summary as at leastone node event from the group consisting of a profile change eventindicating the first ID node changed a profile setting during amonitored event horizon for the first ID node, a transmission powerchange event indicating the first ID node changed an output powersetting during the monitored event horizon, and an environmental changeevent indicating a change in sensor data captured by the first ID nodeduring the monitored event horizon.

254. A monitoring system that identifies an event candidate within awireless node network, the system comprising: a server disposed at a toplevel of the wireless node network; an ID node disposed at a low levelof the wireless node network; a master node disposed at a middle levelof the wireless node network, wherein the master node further comprisesa master node processing unit, a memory storage coupled to the masternode processing unit, the memory storage maintaining event detectionengine code for execution by the master node processing unit, a firstcommunication interface coupled to the master node processing unit andoperative to communicate with the ID node over a first communicationpath, and a second communication interface coupled to the master nodeprocessing unit and operative to communicate with the server over asecond communication path, wherein the first communication path isdifferent from the second communication path;

wherein the master node, when executing the event detection engine codeon the master node processing unit, is operative to cause the firstcommunication interface to listen for one or more broadcast signalsemitted from the ID node without prompting the ID node for transmissionof the one or more broadcast signals from the ID node, detect, via thefirst communication interface, a first advertising signal broadcast bythe ID node, record a first observed parameter in the memory storagebased upon the detected first advertising signal broadcast by the IDnode, successively detect, via the first communication interface, asubsequent group of advertising signals broadcast by the ID node, recorda subsequent group of observed parameters where each are based upon arespective one of the successively received subsequent group ofadvertising signals broadcast by the ID node, generate a firstcheckpoint summary representing a first set of advertising signalscomprising the detected first advertising signal and the successivelydetected subsequent group of advertising signals, the first checkpointsummary comprising a summary observed parameter generated based upon therecorded observed parameter based upon the detected first advertisingsignal broadcast and each of the recorded observed parametersrespectively based upon the successively detected subsequent group ofadvertising signals; and cause the second communication interface toreport the first checkpoint summary over the second communication pathto the server as the event candidate relative to the ID node.

255. The system of embodiment 254, wherein the master node processingunit is further operative to generate the summary observed parameter forthe first checkpoint summary as a statistical representation of theobserved signal strength values for the first set of advertising signalsbroadcast by the ID node.

256. The system of embodiment 255, wherein the statisticalrepresentation of the observed signal strength values comprises one froma group consisting of a mean, a median, an average, a moving averageover a subset window of advertising signals, a moving average over asliding time window, or a weighted average.

257. The system of embodiment 254, wherein each of the first observedparameter and the subsequent group of observed parameters comprises areceived signal strength indicator (RSSI) value reflecting a signalstrength as detected by the master node.

258. The system of embodiment 254, wherein each of the first observedparameter and the subsequent group of observed parameters comprises oneof a plurality of sensor data captured by the master node related to theID node.

259. The system of embodiment 254, wherein the master node processingunit is operative to cause the second communication interface to reportthe first checkpoint summary to the server by being further operativeto: determine if the first checkpoint summary meets a periodic reportinginterval criteria relative to one or more prior checkpoint summariesgenerated by the master node and stored within the memory storage of themaster node; and cause the second communication interface to transmitthe first checkpoint summary to the server as the event candidate onlywhen the first checkpoint summary meets the periodic reporting intervalcriteria.

260. The system of embodiment 254, wherein the master node processingunit is operative to cause the second communication interface to reportthe first checkpoint summary to the server by being further operativeto: increment a checkpoint count upon generating the first checkpointsummary; compare the incremented checkpoint count to a periodicreporting interval criteria relative to one or more prior checkpointsummaries generated by the master node; and cause the secondcommunication interface to transmit the first checkpoint summary to theserver as the event candidate only when the incremented checkpoint countmatches the periodic reporting interval criteria.

261. The system of embodiment 260, wherein the periodic reportinginterval criteria identifies a threshold number of generated checkpointsummaries as a reporting condition for reporting the first checkpointsummary to the server as the event candidate.

262. The system of embodiment 260, wherein the master node processingunit is further operative to: detect, via the first communicationinterface, a profile identifier from the ID node, the profile identifierbeing part of at least one of the detected first advertising signal andthe successively detected subsequent group of advertising signals; andalter the periodic reporting interval criteria based upon an alertprofile corresponding to the profile identifier, the alert profilecomprising a plurality of node management rules related to monitoringthe ID node and reporting to the server.

263. The system of embodiment 254, wherein the master node processingunit is further operative to adjust the summary observed parameter tostatistically summarize the first checkpoint summary with at least oneprevious checkpoint summary generated by the master node and notreported to the server.

264. The system of embodiment 254, wherein the master node processingunit is further operative to: access the memory storage for a previoussummary observed parameter for a previous checkpoint summary; comparethe previous summary observed parameter to the summary observedparameter for the first checkpoint summary to identify a change in astatus of the ID node; and wherein the second communication interfacetransmits the first checkpoint summary to the server as the eventcandidate if the master node processing unit identifies the change inthe status of the ID node by comparing the previous summary observedparameter to the summary observed parameter for the first checkpointsummary.

265. The system of embodiment 264, wherein the change in the status ofthe ID node comprises a monitored node condition when the previoussummary observed parameter for the previous checkpoint summary isdifferent than the summary observed parameter for the first checkpointsummary by more than a threshold level.

266. The system of embodiment 264, wherein the change in the status ofthe ID node identifies the first checkpoint summary as at least one nodeevent from the group consisting of a sporadic event indicating anabbreviated event horizon for the ID node, an online event indicating abeginning of a monitored event horizon for the ID node, a shift eventindicating at least a threshold difference between the previous summaryobserved parameter for the previous checkpoint summary and the summaryobserved parameter for the first checkpoint summary, and an offlineevent indicating an end of the monitored event horizon for the ID node.

267. The system of embodiment 264, wherein the change in the status ofthe ID node identifies the first checkpoint summary as at least one nodeevent from the group consisting of a profile change event indicating theID node changed a profile setting during a monitored event horizon forthe ID node, a transmission power change event indicating the ID nodechanged an output power setting during the monitored event horizon, andan environmental change event indicating a change in sensor datacaptured by the ID node during the monitored event horizon.

268. The system of embodiment 254, wherein the server is operative toreceive the event candidate from the master node and transmit aresponsive adjustment response to the master node based upon the eventcandidate, the responsive adjustment response comprising at least one ofan adjusted profile for the master node, an adjusted profile for the IDnode, and updated context data reflecting the identified eventcandidate.

Further Embodiment F—Systems, Apparatus, and Methods of EnhancedManagement of a Wireless Node Network Based Upon an Event CandidateRelated to Elements of the Wireless Node Network

1. A method for enhanced management of a wireless node network having aplurality of ID nodes, a master node in communication with the ID nodes,and a server in communication with the master node, the methodcomprising: receiving, by the server, an event candidate identified bythe master node, wherein the event candidate is related to a first ofthe ID nodes and represents an updated status related to the first IDnode; generating, by the server, a predictive score for the eventcandidate based upon context data maintained by the server and relatedto the first ID node, wherein the predictive score focuses on whetherthe event candidate corresponds to a node related activity; updating, bythe server, node management information based upon a type of the eventcandidate and the predictive score for the event candidate; andtransmitting, by the server, a management message to the master node,the management message providing at least a portion of the updated nodemanagement information to the master node as feedback to the master nodeused for enhanced management of one or more elements of the wirelessnode network.

2. The method of embodiment 1, wherein the event candidate is related toa subset of the ID nodes including the first ID node.

3. The method of embodiment 1, wherein the updated status related to thefirst ID node comprises a shift in signal strength in what is broadcastby the first ID node.

4. The method of embodiment 1, wherein the step of generating thepredictive score for the event candidate further comprises generatingthe predictive score based upon an evaluation of the event candidateagainst at least a portion of the context data related to the first IDnode.

5. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises scan data related to the first IDnode.

6. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises scan data related to the masternode.

7. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises scan data related to a secondmaster node in the wireless node network.

8. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises scan data related to a second ofthe ID nodes.

9. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises historic data related to thefirst ID node.

10. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises historic data related to themaster node.

11. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises historic data related to a secondmaster node in the wireless node network.

12. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises historic data related to a secondof the ID nodes.

13. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises shipment data related to an itembeing shipped with the first ID node.

14. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises layout data related to ananticipated environment for the first ID node.

15. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises RF data related to an anticipatedsignal path environment for the first ID node.

16. The method of embodiment 4, wherein the portion of the context datarelated to the first ID node comprises third party data originating fromoutside the wireless node network and relating to an anticipatedphysical condition to be faced by the first ID node.

17. The method of embodiment 1, wherein the step of generating thepredictive score for the event candidate further comprises: identifying,by the server, a pattern match between the event candidate and at leasta portion of the context data related to the first ID node; andassigning, by the server, a rating as the predictive score for the eventcandidate based upon the extent the server identifies the pattern matchbetween the event candidate and the portion of the context data relatedto the first ID node.

18. The method of embodiment 1, wherein the step of generating thepredictive score for the event candidate further comprises: comparing,by the server, the event candidate to at least a portion of the contextdata related to the first ID node; and determining, by the server, aprobability rank as the predictive score for the event candidate basedupon the comparison between the event candidate and the portion of thecontext data related to the first ID node.

19. The method of embodiment 1, wherein the predictive score comprises aconfidence factor related to whether the event candidate corresponds tothe node relevant activity.

20. The method of embodiment 1, wherein the node relevant activitycomprises at least one of a detectable physical activity and adetectable electromagnetic activity.

21. The method of embodiment 1, wherein the node relevant activitycomprises an anticipated activity characterized by at least a portion ofthe context data related to the first ID node.

22. The method of embodiment 1, wherein the node relevant activitycomprises a new activity not already characterized by the context datarelated to the first ID node.

23. The method of embodiment 1, wherein the node management informationcomprises node management data maintained by the server, the nodemanagement data relating to one or more ID nodes within the wirelessnode network, the node management data including the context datamaintained by the server and related to the first ID node.

24. The method of embodiment 1, wherein the node management informationcomprises node management data maintained by the server, the nodemanagement data relating to the master node.

25. The method of embodiment 1, wherein the node management informationcomprises a node management rule maintained by the server, the nodemanagement rule defining one or more parameters of an operationalprofile for one or more ID nodes within the wireless node network.

26. The method of embodiment 1, wherein the node management informationcomprises a node management rule maintained by the server, the nodemanagement rule defining one or more parameters of an operationalprofile for the master node.

27. The method of embodiment 1, wherein the node management informationcomprises a node management rule defining one or more parameters on howthe master node identifies the event candidate.

28. The method of embodiment 1, wherein the node management informationcomprises a node management rule defining one or more parameters on howthe master node simplifies a data feed between the master node and theserver.

29. The method of embodiment 1, wherein the updating step furthercomprises transforming, by the server, the node management informationto further indicate a correspondence between the node related activityand the updated status related to the first ID node, the transformationbeing based upon the type of the event candidate and the predictivescore for the event candidate.

30. The method of embodiment 1, wherein the node related activitycomprises movement of at least one of the first ID node, the masternode, and an object near the master node.

31. The method of embodiment 1, wherein the node related activitycomprises exposure to a source of RF interference.

32. The method of embodiment 1, wherein the node related activitycomprises placement of the first ID node within a container.

33. The method of embodiment 1, wherein the transmitting step furthercomprises providing, by the server, the portion of the updated nodemanagement information to the master node as management control inputfor the master node, wherein the control input alters how the masternode operates.

34. The method of embodiment 1, wherein the transmitting step furthercomprises providing, by the server, the portion of the updated nodemanagement information to the master node as management control inputfor the master node, wherein the control input alters how the masternode manages at least one of the ID nodes.

35. The method of embodiment 33, wherein the portion of the updated nodemanagement information provided as the management control inputcomprises an updated node management rule refining how the master nodeidentifies the event candidate.

36. The method of embodiment 33, wherein the portion of the updated nodemanagement information provided as the management control inputcomprises an updated node management rule refining how the master nodesimplifies a data feed between the master node and the server.

37. The method of embodiment 1, wherein the updated status comprises achanged status of the first ID node.

38. The method of embodiment 1, wherein the updated status comprises anunchanged status of the first ID node.

39. The method of embodiment 1, wherein the updated status comprises asummarized checkpoint status of the first ID node.

40. A method for enhanced management of a wireless node network having aplurality of ID nodes, a master node in communication with the ID nodes,and a server in communication with the master node, the methodcomprising: receiving, by the server, an event candidate identified bythe master node, wherein the event candidate is related to a first ofthe ID nodes and represents an updated status related to the first IDnode; ranking, by the server, the event candidate for confidence ofrepresenting a node relevant activity based upon context data maintainedby the server and related to the first ID node; revising, by the server,node management information based upon a type of the event candidate andthe ranking of the event candidate, wherein the node managementinformation is maintained by the server and is related to at least oneof the master node and the first ID node; and transmitting, by theserver, a management message to the master node, the management messageproviding at least a portion of the revised node management informationto the master node as instructional input to be used by the master node.

41. The method of embodiment 40, wherein the step of ranking the eventcandidate further comprises generating a predictive score based upon anevaluation of the event candidate against at least a portion of thecontext data related to the first ID node for confidence of representingthe node relevant activity.

42. The method of embodiment 40, wherein the node relevant activity isan anticipated activity characterized by at least a portion of thecontext data related to the first ID node.

43. The method of embodiment 40, wherein the node relevant activity is anew activity not characterized by a current state of the context dataidentified to be related to the first ID node.

44. The method of embodiment 40, wherein the node management informationcomprises node management data maintained by the server, the nodemanagement data relating to one or more ID nodes within the wirelessnode network, the node management data including the context datamaintained by the server and related to the first ID node.

45. The method of embodiment 40, wherein the node management informationcomprises node management data maintained by the server, the nodemanagement data relating to the master node.

46. The method of embodiment 40, wherein the node management informationcomprises a node management rule maintained by the server, the nodemanagement rule defining one or more parameters of an operationalprofile for one or more ID nodes within the wireless node network.

47. The method of embodiment 40, wherein the node management informationcomprises a node management rule maintained by the server, the nodemanagement rule defining one or more parameters of an operationalprofile for the master node.

48. The method of embodiment 40, wherein the node management informationcomprises a node management rule defining one or more parameters on howthe master node identifies the event candidate.

49. The method of embodiment 40, wherein the node management informationcomprises a node management rule defining one or more parameters on howthe master node simplifies a data feed between the master node and theserver.

50. The method of embodiment 40, wherein the revising step furthercomprises transforming, by the server, the node management informationto further indicate a correspondence between the node relevant activityand the updated status related to the first ID node, the transformationbeing based upon the type of the event candidate and the ranking of theevent candidate.

51. The method of embodiment 50, wherein the node relevant activitycomprises movement of at least one of the first ID node, the masternode, and an object near the master node.

52. The method of embodiment 50, wherein the node relevant activitycomprises exposure to a source of shielding that inhibits communicationbetween the first ID node and the master node.

53. The method of embodiment 50, wherein the node relevant activitycomprises exposure to a source of RF interference.

54. The method of embodiment 50, wherein the node relevant activitycomprises placement of the first ID node within a container.

55. The method of embodiment 40, wherein the instructional input altershow the master node operates.

56. The method of embodiment 40, wherein the instructional input is usedby the master node to control an operation of the master node.

57. The method of embodiment 40, wherein the instructional input altershow the master node manages at least one of the ID nodes.

58. The method of embodiment 40, wherein the instructional input is usedby the master node to cause at least one of the ID nodes to alteroperation.

59. The method of embodiment 55, wherein the instructional inputcomprises an updated node management rule defining how the master nodeidentifies the event candidate.

60. The method of embodiment 55, wherein the instructional inputcomprises an updated node management rule refining how the master nodesimplifies a data feed between the master node and the server.

61. The method of embodiment 40, wherein the updated status comprises achanged status of the first ID node.

62. The method of embodiment 40, wherein the updated status comprises anunchanged status of the first ID node.

63. The method of embodiment 40, wherein the updated status comprises asummarized checkpoint status of the first ID node.

64. A server apparatus for enhanced management of a wireless nodenetwork having a plurality of ID nodes and a master node incommunication with the ID nodes, the apparatus comprising: a serverprocessing unit; a memory storage coupled to the server processing unit,the memory storage maintaining event candidate analytics engine code forexecution by the server processing unit, the memory storage furthermaintaining node management information used to control one or more ofthe ID nodes and the master node as part of managing the wireless nodenetwork, wherein the node management information comprises at leastcontext data describing a contextual environment of the ID nodes andrule data used for node control operations; a network interface coupledto the server processing unit and operative to communicate with themaster node over a network communication path, wherein the networkcommunication path allows the server to directly interact with themaster node but does not allow the server to directly interact with theID nodes; and wherein the server processing unit, when executing theevent candidate analytics engine code maintained on the memory storageand having access to the node management information, is operative toreceive, via the network interface, an event candidate from the masternode, the event candidate being identified by the master node asrepresenting an updated status related to the first ID node, generate aconfidence rating for the event candidate based upon an evaluation ofthe event candidate against at least a portion of the context data, theconfidence rating indicating a degree to which the event candidaterepresents a node relevant activity, update the node managementinformation stored on the memory storage based upon a type of the eventcandidate and the confidence rating for the event candidate, and causethe network interface to transmit a management message to the masternode, the management message providing at least a portion of the updatednode management information to the master node as instructional input tobe used by the master node.

65. The server apparatus of embodiment 64, wherein the instructionalinput is used by the master node to control an operation of the masternode.

66. The server apparatus of embodiment 64, wherein the instructionalinput is used by the master node to cause at least one of the ID nodesto alter operation.

67. The server apparatus of embodiment 64, wherein the node relevantactivity is an anticipated activity characterized by at least a portionof the context data related to the first ID node.

68. The server apparatus of embodiment 64, wherein the node relevantactivity is a new activity not characterized by a current state of thecontext data identified to be related to the first ID node.

69. The server apparatus of embodiment 64, wherein the rule data definesat least one parameter of an operational profile for one or more IDnodes within the wireless node network.

70. The server apparatus of embodiment 64, wherein the rule data definesat least one parameter of an operational profile for the master nodewithin the wireless node network.

71. The server apparatus of embodiment 64, wherein the rule data definesone or more parameters on how the master node identifies the eventcandidate.

72. The server apparatus of embodiment 64, wherein the rule data definesone or more parameters on how the master node simplifies a data feedcoupling the master node and network interface of the server apparatus.

73. The server apparatus of embodiment 64, wherein the node managementinformation comprises further context data relating to the master node.

74. The server apparatus of embodiment 64, wherein the server processingunit is operative to update the node management information stored onthe memory storage by being further operative to transform the nodemanagement information to further indicate a correspondence between thenode relevant activity and the updated status related to the first IDnode.

75. The server apparatus of embodiment 74, wherein the node relevantactivity comprises at least one of a detectable physical activity and adetectable electromagnetic activity.

76. The server apparatus of embodiment 74, wherein the server processingunit is operative to transform the node management information basedupon the type of the event candidate and the confidence rating of theevent candidate.

77. The server apparatus of embodiment 74, wherein the node relevantactivity comprises movement of at least one of the first ID node, themaster node, and an object near the master node.

78. The server apparatus of embodiment 74, wherein the node relevantactivity comprises exposure to a source of shielding that inhibitscommunication between the first ID node and the master node.

79. The server apparatus of embodiment 74, wherein the node relevantactivity comprises exposure to a source of RF interference.

80. The server apparatus of embodiment 74, wherein the node relevantactivity comprises placement of the first ID node within a container.

81. The server apparatus of embodiment 64, wherein the instructionalinput alters how the master node operates.

82. The server apparatus of embodiment 64, wherein the instructionalinput alters how the master node manages at least one of the ID nodes.

83. The server apparatus of embodiment 81, wherein the instructionalinput comprises updated rule data defining how the master nodeidentifies the event candidate.

84. The server apparatus of embodiment 81, wherein the instructionalinput comprises updated rule data refining how the master nodesimplifies a data fee between the master node and the server.

85. The server apparatus of embodiment 64, wherein the updated statuscomprises a changed status of the first ID node.

86. The server apparatus of embodiment 64, wherein the updated statuscomprises an unchanged status of the first ID node.

87. The server apparatus of embodiment 64, wherein the updated statuscomprises a summarized checkpoint status of the first ID node.

88. An enhanced node management system for a wireless node networkhaving a plurality of ID nodes, the system comprising: a master nodedisposed within the wireless node network that executes an eventdetection engine code to become operative to generate a report messageregarding an event candidate representing an updated status related to afirst of the ID nodes, and receive a management message in response tothe generated report message; and a server in communication with themaster node over a first communication path, the server maintaining nodemanagement information used to control one or more of the ID nodes andthe master node as part of managing the wireless node network, whereinthe node management information comprises at least context datadescribing a contextual operating environment of the ID nodes and ruledata used for node control operations of the ID nodes and the masternode, wherein when the server executes an event candidate analyticsengine code maintained on the server, the server becomes operative to:receive the report message from the master node, extract the eventcandidate from the report message, the event candidate being identifiedby the master node as representing the updated status related to thefirst ID node, generate a confidence rating for the event candidatebased upon an evaluation of the event candidate compared to at least aportion of the context data maintained by the server, the confidencerating indicating a degree to which the event candidate represents anode relevant activity, update the node management information basedupon a type of the event candidate and the confidence rating for theevent candidate, and transmit the management message to the master node,the management message providing at least a portion of the updated nodemanagement information to the master node as instructional input to beused by the master node.

89. The system of embodiment 88, wherein the instructional input is usedby the master node to control an operation of the master node.

90. The system of embodiment 88, wherein the instructional input is usedby the master node to cause at least one of the ID nodes to alteroperation.

91. The system of embodiment 88, wherein the node relevant activitycomprises at least one of a detectable physical activity and adetectable electromagnetic activity.

92. The system of embodiment 88, wherein the node relevant activity isan anticipated activity characterized by at least a portion of thecontext data that is related to the first ID node.

93. The system of embodiment 88, wherein the node relevant activity is anew activity not characterized by the context data identified as relatedto the first ID node.

94. The system of embodiment 88, wherein the rule data defines at leastone parameter of an operational profile for one or more ID nodes.

95. The system of embodiment 88, wherein the rule data defines at leastone parameter of an operational profile for the master node.

96. The system of embodiment 88, wherein the server updates the nodemanagement information by transforming the node management informationto further indicate a correspondence between the node relevant activityand the updated status related to the first ID node.

97. The system of embodiment 96, wherein the server transforms the nodemanagement information based upon the type of the event candidate andthe confidence rating of the event candidate.

98. The system of embodiment 96, wherein the node relevant activitycomprises movement of at least one of the first ID node, the masternode, and an object near the master node.

99. The system of embodiment 96, wherein the node relevant activitycomprises exposure to a source of shielding that inhibits communicationbetween the first ID node and the master node.

100. The system of embodiment 96, wherein the node relevant activitycomprises exposure to a source of RF interference.

101. The system of embodiment 96, wherein the node relevant activitycomprises placement of the first ID node within a container.

102. The system of embodiment 88, wherein the server is operative totransmit the management message to cause the master node to alter howthe master node operates.

103. The system of embodiment 88, wherein the server is operative totransmit the management message to cause the master node to send asecond management message to at least one of the ID nodes, the secondmanagement message causing the one of the ID nodes to alter how the oneof the ID nodes operates.

104. The system of embodiment 88, wherein the portion of the revisednode management information provided as the instructional inputcomprises updated rule data.

105. The system of embodiment 88, wherein the updated status comprises achanged status of the first ID node.

106. The system of embodiment 88, wherein the updated status comprisesan unchanged status of the first ID node.

107. The system of embodiment 88, wherein the updated status comprises asummarized checkpoint status of the first ID node.

108. An enhanced node management system for a wireless node networkhaving a plurality of ID nodes, the system comprising: a server; amaster node disposed within the wireless node network in communicationwith the server over a first communication path and in communicationwith the ID nodes over a second communication path distinct from thefirst communication path, wherein when the master node executes a firstengine code, the master node becomes operative to: detect a firstupdated status related to a first of the ID nodes, wherein the detectedfirst status is represented by a first event candidate, detect a secondupdated status related to a second of the ID nodes, wherein the detectedsecond status is represented by a second event candidate, transmit thefirst event candidate and the second event candidate by the master nodeto the server over the first communication path, and receive amanagement message in response to the transmitting the first eventcandidate and the second event candidate; wherein the server maintainsnode management information used to control one or more of the ID nodesand the master node as part of managing the wireless node network,wherein the node management information comprises at least context datadescribing a contextual operating environment of the ID nodes and ruledata used for node control operations of the ID nodes and the masternode; and wherein when the server executes a second engine codemaintained on the server, the server becomes operative to: receive thefirst event candidate and the second event candidate from the masternode, generate a first confidence rating for the first event candidatebased upon an evaluation of the first event candidate compared to atleast a first portion of the context data maintained by the server, thefirst confidence rating indicating a degree to which the first eventcandidate represents a node relevant activity, generate a secondconfidence rating for the second event candidate based upon anevaluation of the second event candidate compared to at least a secondportion of the context data maintained by the server, the secondconfidence rating indicating a degree to which the second eventcandidate represents the node relevant activity, compare the firstconfidence rating and the second confidence rating to determine acombined confidence rating reflecting a degree to which the detectedfirst change and the detected second change represent a patterncorresponding to the node relevant activity, update the node managementinformation based upon a type of the first event candidate, a type ofthe second event candidate, and the combined confidence rating, andtransmit the management message to the master node, the managementmessage providing at least a portion of the updated node managementinformation to the master node as instructional input to be used by themaster node.

It should be emphasized that the sequence of operations to perform anyof the methods and variations of the methods described in theembodiments herein are merely exemplary, and that a variety of sequencesof operations may be followed while still being true and in accordancewith the principles of the present invention.

At least some portions of exemplary embodiments outlined above may beused in association with portions of other exemplary embodiments tobetter manage and locate nodes in a wireless node network or use suchnodes and network elements as part of a hierarchical node network.Moreover, at least some of the exemplary embodiments disclosed hereinmay be used independently from one another and/or in combination withone another and may have applications to devices and methods notdisclosed herein.

Those skilled in the art will appreciate that embodiments may provideone or more advantages, and not all embodiments necessarily provide allor more than one particular advantage as set forth here. Additionally,it will be apparent to those skilled in the art that variousmodifications and variations can be made to the structures andmethodologies described herein. Thus, it should be understood that theinvention is not limited to the subject matter discussed in thedescription. Rather, the present invention is intended to covermodifications and variations.

What is claimed is:
 1. A monitoring system that identifies an eventcandidate within a wireless node network, the system comprising: aserver disposed at a top level of the wireless node network; an ID nodedisposed at a low level of the wireless node network; a master nodedisposed at a middle level of the wireless node network, wherein themaster node further comprises a master node processing unit, a memorystorage coupled to the master node processing unit, the memory storagemaintaining event detection engine code for execution by the master nodeprocessing unit, a first communication interface coupled to the masternode processing unit and operative to communicate with the ID node overa first communication path, and a second communication interface coupledto the master node processing unit and operative to communicate with theserver over a second communication path, wherein the first communicationpath is different from the second communication path; wherein the masternode, when executing the event detection engine code on the master nodeprocessing unit, is operative to detect, via the first communicationinterface, a first set of advertising signals broadcast by a first ofthe ID nodes over the first communication path, generate a firstcheckpoint summary representing the first set of advertising signalsdetected by the first communication interface, detect, via the firstcommunication interface, a second set of advertising signals broadcastby the first ID node over the first communication path after the firstID node broadcasts the first set of advertising signals, generate asecond checkpoint summary representing the second set of advertisingsignals detected by the first communication interface, compare anobserved parameter for each of the first checkpoint summary and thesecond checkpoint summary, identify the event candidate based upon thecomparison of the observed parameter for each of the first checkpointsummary and the second checkpoint summary, and cause the secondcommunication interface to report the identified event candidate to theserver over the second communication path; and wherein the server isoperative to receive the identified event candidate from the master nodeand transmit a responsive adjustment response to the master node basedupon the identified event candidate, the responsive adjustment responsecomprising at least one of an adjusted profile for the master node, anadjusted profile for the ID node, and updated context data reflectingthe identified event candidate.
 2. The system of claim 1, wherein thesecond communication interface of the master node is operative totransmit a message to the server when reporting the identified eventcandidate, the message comprising a reduced monitoring data feed aboutthe ID node that at least includes summary information indicating anobserved change between the first set of advertising signals representedby the first checkpoint summary and the second set of advertisingsignals represented by the second checkpoint summary.
 3. The system ofclaim 1, wherein the observed parameter for the first checkpoint summarycomprises a statistical representation of the observed signal strengthvalues for the first set of advertising signals; and wherein theobserved parameter for the second checkpoint summary comprises thestatistical representation of the observed signal strength values forthe second set of advertising signals.
 4. The system of claim 3, whereinthe statistical representation of the observed signal strength valuescomprises one from a group consisting of a mean, a median, an average, amoving average over a subset window of advertising signals, a movingaverage over a sliding time window, or a weighted average.
 5. The systemof claim 3, wherein the observed signal strength value comprises areceived signal strength indicator (RSSI) reflecting a signal strengthas detected by the first communication interface.
 6. The system of claim3, wherein the master node is operative to identify the event candidateby being further operative to identify the event candidate as an onlineevent for the ID node when (a) a detected time gap between successiveones of the first set of advertising signals and the second set ofadvertising signals is less than the threshold time gap and (b) themaster node has received at least a threshold number of advertisingsignals from the ID node in the first set and the second set.
 7. Thesystem of claim 3, wherein the master node is operative to identify theevent candidate by being further operative to identify the eventcandidate as a shift event for the ID node when a difference between theobserved parameter for the first checkpoint summary and the observedparameter for the second checkpoint summary is at least a thresholdvalue.
 8. The system of claim 1, wherein the master node is operative toidentify the event candidate by being further operative to identify theevent candidate as an offline event when a detected time gap between anysuccessive ones of the second set of advertising signals after detectingthe first set of advertising signals is greater than the threshold timegap during an event horizon for the ID node.
 9. The system of claim 1,wherein the master node is operative to identify the event candidate bybeing further operative to identify the event candidate as a sporadicevent when the first communication interface detects at least oneadvertising signal from the ID node but does not detect at least athreshold number of advertising signals from the ID node within adefined period of time from when the first communication interfacedetects the at least one advertising signal.
 10. The system of claim 1,wherein the master node is operative to identify the event candidate bybeing further operative to identify the event candidate as a checkpointevent when a periodic reporting interval ends and based upon thecomparison of the observed parameter for the first checkpoint summaryand the observed parameter for the second checkpoint summary.
 11. Thesystem of claim 10, wherein the master node is further operative toidentify a profile identifier from the ID node, the profile identifierbeing part of at least one of the advertising signals in either of thefirst set of advertising signals and the second set of advertisingsignals; and alter the periodic reporting interval based upon an alertprofile corresponding to the profile identifier, the alert profilecomprising a plurality of node management rules related to monitoringthe ID node and reporting to the server.
 12. The system of claim 11,wherein periodic reporting interval comprises a threshold time periodadjustable by the node processing unit in response to identifying theprofile identifier.
 13. The system of claim 11, wherein periodicreporting interval comprises a threshold number of signal receptionsadjustable by the node processing unit in response to identifying theprofile identifier.
 14. The system of claim 1, wherein the master nodeis operative to identify the event candidate by being further operativeto identify the event candidate as a profile change event when thecomparison of the observed parameter for each of the first checkpointsummary and the second checkpoint summary indicates a first observedprofile setting reflected in the first set of advertising signals isdifferent than a second observed profile setting reflected in the secondset of advertising signals.
 15. The system of claim 14, wherein thefirst observed profile setting and second observed profile settingrelate to operation of the ID node.
 16. The system of claim 14, whereinthe first observed profile setting and second observed profile settingrelate to operation of the master node.
 17. The system of claim 1,wherein the master node is operative to identify the event candidate bybeing further operative to identify the event candidate as atransmission power change event when the comparison of the observedparameter for each of the first checkpoint summary and the secondcheckpoint summary indicates a first observed output power settingreflected in the first set of advertising signals is different than asecond observed output power setting reflected in the second set ofadvertising signals.
 18. The system of claim 1, wherein the master nodeis operative to identify the event candidate by being further operativeto identify the event candidate as an environmental change event whenthe comparison of the observed parameter for each of the firstcheckpoint summary and the second checkpoint summary indicates a secondsensor data value associated with the second set of advertising signalsis different than a first sensor data value associated with the firstset of advertising signals.
 19. The system of claim 1, wherein themaster node is operative to identify the event candidate by beingfurther operative to identify the event candidate as an environmentalchange event when the comparison of the observed parameter for each ofthe first checkpoint summary and the second checkpoint summary indicatesa second sensor data value associated with the second set of advertisingsignals reflects a departure from a first sensor data value associatedwith the first set of advertising signals, wherein the departure is morethan a threshold difference.
 20. A master node apparatus for enhancedmonitoring for an event candidate within a wireless node network havinga plurality of ID nodes and a server, the master node apparatuscomprising: a node processing unit; a memory storage coupled to the nodeprocessing unit, the memory storage maintaining event detection enginecode for execution by the node processing unit; a first communicationinterface coupled to the node processing unit and operative tocommunicate with at least a first of the ID nodes over a firstcommunication path; a second communication interface coupled to the nodeprocessing unit and operative to communicate with the server over asecond communication path; and wherein the node processing unit, whenexecuting the event detection engine code maintained on the memorystorage, is operative to detect, via the first communication interface,a first set of advertising signals broadcast by a first of the ID nodes,generate a first checkpoint summary representing the first set ofadvertising signals detected by the first communication interface,detect, via the first communication interface, a second set ofadvertising signals broadcast by the first ID node after the first IDnode broadcasts the first set of advertising signals, generate a secondcheckpoint summary representing the second set of advertising signalsdetected by the first communication interface, compare an observedparameter for each of the first checkpoint summary and the secondcheckpoint summary, identify the event candidate based upon thecomparison of the observed parameter for each of the first checkpointsummary and the second checkpoint summary, and cause the secondcommunication interface to report the identified event candidate to theserver over the second communication path.
 21. The master node apparatusof claim 20, wherein the second communication interface is operative totransmit a message to the server when reporting the identified eventcandidate, the message comprising a reduced monitoring data feed aboutthe first ID node that at least includes summary information indicatingan observed change between the first set of advertising signalsrepresented by the first checkpoint summary and the second set ofadvertising signals represented by the second checkpoint summary. 22.The master node apparatus of claim 20, wherein the observed parameterfor the first checkpoint summary comprises a statistical representationof the observed signal strength values for the first set of advertisingsignals; and wherein the observed parameter for the second checkpointsummary comprises the statistical representation of the observed signalstrength values for the second set of advertising signals.
 23. Themaster node apparatus of claim 22, wherein the statisticalrepresentation of the observed signal strength values comprises one froma group consisting of a mean, a median, an average, a moving averageover a subset window of advertising signals, a moving average over asliding time window, or a weighted average.
 24. The master nodeapparatus of claim 22, wherein the observed signal strength valuecomprises a received signal strength indicator (RSSI) reflecting asignal strength as detected by the first communication interface. 25.The master node apparatus of claim 22, wherein the node processing unitis operative to identify the event candidate by being further operativeto identify the event candidate as an online event for the first ID nodewhen (a) a detected time gap between successive ones of the first set ofadvertising signals and the second set of advertising signals is lessthan the threshold time gap and (b) the first communication interfacehas received at least a threshold number of advertising signals from thefirst ID node in the first set and the second set.
 26. The master nodeapparatus of claim 22, wherein the node processing unit is operative toidentify the event candidate by being further operative to identify theevent candidate as a shift event for the first ID node when a differencebetween the observed parameter for the first checkpoint summary and theobserved parameter for the second checkpoint summary is at least athreshold value.
 27. The master node apparatus of claim 22, wherein thenode processing unit is operative to identify the event candidate bybeing further operative to identify the event candidate as an offlineevent when a detected time gap between any successive ones of the secondset of advertising signals after detecting the first set of advertisingsignals is greater than the threshold time gap during an event horizonfor the first ID node.
 28. The master node apparatus of claim 20,wherein the node processing unit is operative to identify the eventcandidate by being further operative to identify the event candidate asa sporadic event when the first communication interface detects at leastone advertising signal from the first ID node but does not detect atleast a threshold number of advertising signals from the first ID nodewithin a defined period of time from when the first communicationinterface detects the at least one advertising signal.
 29. The masternode apparatus of claim 20, wherein the node processing unit isoperative to identify the event candidate by being further operative toidentify the event candidate as a checkpoint event when a periodicreporting interval ends and based upon the comparison of the observedparameter for the first checkpoint summary and the observed parameterfor the second checkpoint summary.
 30. The master node apparatus ofclaim 29, wherein the node processing unit is further operative toidentify a profile identifier from the first ID node, the profileidentifier being part of at least one of the advertising signals ineither of the first set of advertising signals and the second set ofadvertising signals; and alter the periodic reporting interval basedupon an alert profile corresponding to the profile identifier, the alertprofile comprising a plurality of node management rules related tomonitoring the first ID node and reporting to the server.
 31. The masternode apparatus of claim 30, wherein periodic reporting intervalcomprises a threshold time period adjustable by the node processing unitin response to identifying the profile identifier.
 32. The master nodeapparatus of claim 30, wherein periodic reporting interval comprises athreshold number of signal receptions adjustable by the node processingunit in response to identifying the profile identifier.
 33. The masternode apparatus of claim 20, wherein the node processing unit isoperative to identify the event candidate by being further operative toidentify the event candidate as a profile change event when thecomparison of the observed parameter for each of the first checkpointsummary and the second checkpoint summary indicates a first observedprofile setting reflected in the first set of advertising signals isdifferent than a second observed profile setting reflected in the secondset of advertising signals.
 34. The master node apparatus of claim 33,wherein the first observed profile setting and second observed profilesetting relate to operation of the first ID node.
 35. The master nodeapparatus of claim 33, wherein the first observed profile setting andsecond observed profile setting relate to operation of the master node.36. The master node apparatus of claim 20, wherein the node processingunit is operative to identify the event candidate by being furtheroperative to identify the event candidate as a transmission power changeevent when the comparison of the observed parameter for each of thefirst checkpoint summary and the second checkpoint summary indicates afirst observed output power setting reflected in the first set ofadvertising signals is different than a second observed output powersetting reflected in the second set of advertising signals.
 37. Themaster node apparatus of claim 20, wherein the node processing unit isoperative to identify the event candidate by being further operative toidentify the event candidate as an environmental change event when thecomparison of the observed parameter for each of the first checkpointsummary and the second checkpoint summary indicates a second sensor datavalue associated with the second set of advertising signals is differentthan a first sensor data value associated with the first set ofadvertising signals.
 38. The master node apparatus of claim 20, whereinthe node processing unit is operative to identify the event candidate bybeing further operative to identify the event candidate as anenvironmental change event when the comparison of the observed parameterfor each of the first checkpoint summary and the second checkpointsummary indicates a second sensor data value associated with the secondset of advertising signals reflects a departure from a first sensor datavalue associated with the first set of advertising signals, wherein thedeparture is more than a threshold difference.
 39. The master nodeapparatus of claim 20, wherein the node processing unit is furtheroperative to receive, via the second communication interface, anadjustment response from the server based upon the event candidate. 40.The master node apparatus of claim 39, wherein the adjustment responsecomprises an adjusted profile for at least one of the master node andthe first ID node.
 41. The master node apparatus of claim 40, whereinthe adjustment response comprises an adjusted profile for at least oneof the other ID nodes.
 42. The master node apparatus of claim 39,wherein the adjustment response comprises updated context datareflecting the reported event candidate.
 43. A method for enhancedmonitoring for an event candidate within a wireless node network havinga plurality of ID nodes, a master node in communication with the IDnodes, and a server in communication with the master node, comprisingthe steps of: receiving, by the master node, a first set of advertisingsignals broadcast by a first of the ID nodes; generating, by the masternode, a first checkpoint summary representing the first set ofadvertising signals received by the master node; receiving, by themaster node, a second set of advertising signals broadcast by the firstID node after the first ID node broadcasts the first set of advertisingsignals; generating, by the master node, a second checkpoint summaryrepresenting the second set of advertising signals received by themaster node; identifying, by the master node, the event candidate basedupon a comparison of an observed parameter for each of the firstcheckpoint summary and the second checkpoint summary; and reporting, bythe master node to the server, the event candidate relative to the firstID node.
 44. The method of claim 43, wherein the reporting step furthercomprises simplifying, by the master node, a data feed about the firstID node by sending the event candidate to the server as summaryinformation reflecting an observed change between the first set ofadvertising signals represented by the first checkpoint summary and thesecond set of advertising signals represented by the second checkpointsummary.
 45. The method of claim 43, wherein the observed parameter forthe first checkpoint summary comprises a statistical representation ofthe observed signal strength values for the first set of advertisingsignals; and wherein the observed parameter for the second checkpointsummary comprises the statistical representation of the observed signalstrength values for the second set of advertising signals.
 46. Themethod of claim 45, wherein the statistical representation of theobserved signal strength values comprises one from a group consisting ofa mean, a median, an average, a moving average over a subset window ofadvertising signals, a moving average over a sliding time window, or aweighted average.
 47. The method of claim 43, wherein each of theobserved signal strength values comprises a received signal strengthindicator (RSSI) reflecting a signal strength as detected by the masternode.
 48. The method of claim 43, wherein the step of identifying theevent candidate further comprises identifying, by the master node, theevent candidate as an online event for the first ID node when (a) adetected time gap between successive ones of the first set ofadvertising signals and the second set of advertising signals is lessthan the threshold time gap and (b) the master node has received atleast a threshold number of advertising signals from the first ID nodein the first set and the second set.
 49. The method of claim 43, whereinthe step of identifying the event candidate further comprisesidentifying, by the master node, the event candidate as a shift eventfor the first ID node when a difference between the observed parameterfor the first checkpoint summary and the observed parameter for thesecond checkpoint summary is at least a threshold value.
 50. The methodof claim 43, wherein the step of identifying the event candidate furthercomprises identifying, by the master node, the event candidate as anoffline event when a detected time gap between any successive ones ofthe second set of advertising signals after detecting the first set ofadvertising signals is greater than the threshold time gap during anevent horizon for the first ID node as monitored by the master node. 51.The method of claim 43, wherein the step of identifying the eventcandidate further comprises identifying, by the master node, the eventcandidate as a sporadic event when the master node receives at least oneadvertising signal from the first ID node but does not receive at leasta threshold number of advertising signals from the first ID node withina defined period of time from when the master node receives the at leastone advertising signal.
 52. The method of claim 43, wherein the step ofidentifying the event candidate further comprises identifying, by themaster node, the event candidate as a checkpoint event when a periodicreporting interval ends and based upon the comparison of the observedparameter for the first checkpoint summary and the observed parameterfor the second checkpoint summary.
 53. The method of claim 52 furthercomprising: detecting, by the master node, a profile identifier from thefirst ID node, the profile identifier being part of at least one of theadvertising signals in the first set of advertising signals and thesecond set of advertising signals; and altering, by the master node, theperiodic reporting interval based upon an alert profile corresponding tothe profile identifier, the alert profile comprising a plurality of nodemanagement rules related to monitoring the first ID node and reportingto the server.
 54. The method of claim 53, wherein the periodicreporting interval comprises a threshold time period adjustable by themaster node.
 55. The method of claim 53, wherein the periodic reportinginterval comprises a threshold number of signal receptions adjustable bythe master node.
 56. The method of claim 52 further comprising resettinginformation collected based upon at least the first set of advertisingsignals and the second set of advertising signals after reporting thecheckpoint event to the server by the master node for data reductionpurposes on the master node.
 57. The method of claim 43, wherein thestep of identifying the event candidate further comprises identifying,by the master node, the event candidate as a profile change event whenthe comparison of the observed parameter for each of the firstcheckpoint summary and the second checkpoint summary indicates a firstobserved profile setting reflected in the first set of advertisingsignals is different than a second observed profile setting reflected inthe second set of advertising signals.
 58. The method of claim 57,wherein the first observed profile setting and second observed profilesetting relate to operation of the first ID node.
 59. The method ofclaim 57, wherein the first observed profile setting and second observedprofile setting relate to operation of the master node.
 60. The methodof claim 43, wherein the step of identifying the event candidate furthercomprises identifying, by the master node, the event candidate as atransmission power change event when the comparison of the observedparameter for each of the first checkpoint summary and the secondcheckpoint summary indicates a first observed output power settingreflected in the first set of advertising signals is different than asecond observed output power setting reflected in the second set ofadvertising signals.
 61. The method of claim 43, wherein the step ofidentifying the event candidate further comprises identifying, by themaster node, the event candidate as an environmental change event whenthe comparison of the observed parameter for each of the firstcheckpoint summary and the second checkpoint summary indicates a secondsensor data value associated with the second set of advertising signalsis different than a first sensor data value associated with the firstset of advertising signals.
 62. The method of claim 43, wherein the stepof identifying the event candidate further comprises identifying, by themaster node, the event candidate as an environmental change event whenthe comparison of the observed parameter for each of the firstcheckpoint summary and the second checkpoint summary indicates a secondsensor data value associated with the second set of advertising signalsreflects a departure from a first sensor data value associated with thefirst set of advertising signals, wherein the departure is more than athreshold difference.
 63. The method of claim 43 further comprisingreceiving, by the master node, an adjustment response from the serverbased upon the event candidate.
 64. The method of claim 63, wherein theadjustment response comprises an adjusted profile for at least one ofthe master node and the first ID node.
 65. The method of claim 64,wherein the adjustment response comprises an adjusted profile for atleast one of the other ID nodes.
 66. The method of claim 63, wherein theadjustment response comprises updated context data reflecting thereported event candidate.